Skip to content

🧠 Decision Framework

This document provides a structured framework for making consistent, value-aligned decisions across the GetCimple platform. It builds upon the core principles and reasoning frameworks established in our First Principles document.

πŸ“Œ Purpose: To ensure decisions at all levels of GetCimple's development and operation consistently align with our core values and stakeholder needs.

🌟 Framework Overview

The GetCimple Decision Framework creates a consistent approach to evaluating options based on our dual-stakeholder focus. It helps teams make decisions that create win-win outcomes for directors (oversight) and management teams (implementation).

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                         β”‚         β”‚                         β”‚
β”‚   Director Perspective  β”‚         β”‚  Management Perspective β”‚
β”‚   (Oversight Layer)     β”‚         β”‚  (Implementation Layer) β”‚
β”‚                         β”‚         β”‚                         β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
            β”‚                                     β”‚
            β–Ό                                     β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                         β”‚         β”‚                         β”‚
β”‚   Value Questions       β”‚         β”‚   Value Questions       β”‚
β”‚   - Liability Reduction β”‚         β”‚   - Implementation      β”‚
β”‚   - Time Efficiency     β”‚         β”‚     Clarity             β”‚
β”‚   - Oversight Quality   β”‚         β”‚   - Workload Balance    β”‚
β”‚                         β”‚         β”‚   - Communication Ease  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜         β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
            β”‚                                     β”‚
            β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                              β–Ό
                     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
                     β”‚                 β”‚
                     β”‚  Decision       β”‚
                     β”‚  Evaluation     β”‚
                     β”‚                 β”‚
                     β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                              β”‚
                              β–Ό
              β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
              β”‚                             β”‚
              β”‚  Documentation & Validation β”‚
              β”‚                             β”‚
              β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ“‹ Decision Types

This framework applies to different types of decisions:

  1. Strategic Decisions: High-impact choices about platform direction, feature prioritization, and market positioning
  2. Design Decisions: Choices about user experience, workflows, and interface elements
  3. Technical Decisions: Architecture, technology stack, and implementation approaches
  4. Operational Decisions: Day-to-day choices about support, communication, and processes

πŸ”„ Decision Process

1. Define the Decision Context

Before evaluating options, establish:

  • Decision Statement: Clearly articulate what decision needs to be made
  • Stakeholder Impact: Identify which stakeholders will be affected
  • Constraints: Recognize time, resource, or technical limitations
  • Decision Urgency: Determine timeline requirements

2. Generate Options

  • Brainstorm potential approaches
  • Include the "do nothing" option where relevant
  • Consider both conventional and innovative approaches
  • Aim for 3-5 viable options

3. Evaluate Against Core Values

For each option, rate alignment with our core values (1-5 scale):

Value Low Alignment (1) High Alignment (5)
Simplicity Adds complexity or cognitive load Reduces complexity or makes simpler
Stakeholder-Centric Benefits only one stakeholder Creates win-win for both stakeholders
Calm Productivity Creates urgency or stress Promotes sustainable pace
Pragmatic Profitability Resource-intensive with low value Efficient use of resources with high value
Real-World Utility Theoretical benefit only Immediate practical utility

4. Apply Dual Stakeholder Lens

For each option, evaluate:

Director Perspective (Oversight Layer)

  • Time Value: How efficiently does this use director time?
  • Liability Reduction: Does this help demonstrate due diligence?
  • Oversight Clarity: Does this improve governance transparency?
  • Decision Support: Does this facilitate better board decisions?

Management Perspective (Implementation Layer)

  • Implementation Clarity: Are expectations and tasks clearly defined?
  • Workload Balance: Is the implementation effort reasonable?
  • Upward Communication: Does this help communicate compliance to the board?
  • Operational Integration: Does this fit with existing operations?

5. Document and Decide

Document your decision process:

Decision: [Brief description of the decision]
Options Considered: [List of options evaluated]
Selected Approach: [The chosen option]
Rationale:
- [Core value alignment]
- [Director perspective benefits]
- [Management perspective benefits]
- [Other considerations]
Stakeholder Impact: [How this affects each stakeholder]
Implementation Plan: [Next steps to execute the decision]

πŸ“Š Decision Matrix Template

Use this matrix to evaluate options against our core criteria:

Option Simplicity (1-5) Stakeholder-Centric (1-5) Calm Productivity (1-5) Pragmatic Profitability (1-5) Real-World Utility (1-5) Director Value (1-5) Management Value (1-5) Total Score
Option 1
Option 2
Option 3
Option 4

🚩 Decision Red Flags

Watch for these warning signs that a decision may not align with our principles:

  • Single Stakeholder Focus: Benefits only directors or only management
  • Complex for Complexity's Sake: Adds unnecessary sophistication
  • Technical Interest-Driven: Prioritizes interesting technology over user value
  • High Cognitive Load: Requires significant mental effort to understand
  • Urgency Without Purpose: Rushed without clear justification
  • Narrow Perspective: Fails to consider all stakeholder viewpoints

πŸ’‘ Decision Examples

Feature Prioritization Example

Decision: Should we prioritize developing the "Executive Dashboard" or "Policy Workflow Automation"?

Decision Matrix:

Option Simplicity Stakeholder-Centric Calm Productivity Pragmatic Profitability Real-World Utility Director Value Management Value Total
Executive Dashboard 4 3 4 3 4 5 2 25
Policy Workflow Automation 3 5 5 4 5 4 5 31

Selected Approach: Policy Workflow Automation

Rationale:

  • Stakeholder Balance: Creates stronger win-win between directors and management
  • Management Value: Significantly reduces administrative burden for management
  • Director Value: Still provides high value to directors through improved oversight
  • Calm Productivity: Reduces urgency and ad-hoc requests between governance layers

Design Decision Example

Decision: How should we design the Essential Eight compliance status indicators?

Options:

  1. Detailed percentage-based compliance metrics
  2. Simple traffic light system (Red/Yellow/Green)
  3. Five-level maturity indicators with detailed breakdowns
  4. Text-only descriptive status
  5. Dual-indicator system showing current vs. target maturity

Selected Approach: Dual-indicator system showing current vs. target maturity with progress visualization

Rationale:

  • Simplicity: Clear visualization of both current state and goal in a single view
  • Stakeholder-Centric: Provides directors with progress context while showing management teams their implementation targets
  • Real-World Utility: Maps directly to ACSC maturity model with decimal precision for tracking progress
  • Pragmatic Profitability: Focuses attention on gap between current state and target rather than absolute values

πŸ“‹ How to Use This Framework

This decision framework should be applied in the following contexts:

  1. Product Planning: When prioritizing the roadmap and determining feature scope
  2. Design Reviews: When evaluating design approaches and interface elements
  3. Technical Planning: When making architecture and technology stack decisions
  4. Team Processes: When establishing workflows and communication patterns

For significant decisions, document the evaluation process and store it in the project repository for future reference.