Back Send feedback to ilkka.kuivanen@me.com

Markdown snippets

This page is intended to function as copy-paste-helper for note-taking, brainstorming, refreshing memory or simply for inspiration.

Strategy & Planning: Milestone

<!--
template_type: milestone
project: [project_name]
status: [planning|active|completed]
priority: [high|medium|low]
-->

# πŸ”οΈ Milestone: [milestone_name] <!-- Clear, descriptive name for this milestone -->

**Status:** 🟑 In Progress | 🟒 On Track | πŸ”΄ At Risk | βœ… Complete

- **πŸ“† Target Date:**
  - [target_date] <!-- YYYY-MM-DD format -->
- **πŸ“† Completion Date:**
  - [completion_date] <!-- YYYY-MM-DD format, filled when completed -->
- **🎯 Objective:**
  - [objective] <!-- Clear statement of what this milestone achieves -->
- **⏱️ Effort Estimate:**
  - Total hours: [total_hours] <!-- Estimated hours needed -->
  - Team members needed: [team_members_needed] <!-- Number of people required -->
- **πŸ“  Key Results:**
  - [ ] **KR1** (Priority: [priority_1] <!-- high|medium|low -->): [kr_1_description] <!-- What specific outcome will be achieved -->
    - Success criteria: [success_criteria_1] <!-- Measurable metrics or conditions -->
    - Owner: [owner_1] <!-- Person responsible for this KR -->
  - [ ] **KR2** (Priority: [priority_2] <!-- high|medium|low -->): [kr_2_description] <!-- What specific outcome will be achieved -->
    - Success criteria: [success_criteria_2] <!-- Measurable metrics or conditions -->
    - Owner: [owner_2] <!-- Person responsible for this KR -->
  - [ ] **KR3** (Priority: [priority_3] <!-- high|medium|low -->): [kr_3_description] <!-- What specific outcome will be achieved -->
    - Success criteria: [success_criteria_3] <!-- Measurable metrics or conditions -->
    - Owner: [owner_3] <!-- Person responsible for this KR -->
- **πŸ”— Context & Dependencies:**
  - Related milestones: [related_milestones] <!-- Links or references to connected milestones -->
  - Dependencies: [dependencies] <!-- What must be completed before this milestone -->
  - Stakeholders: [stakeholders] <!-- People who need to be involved or informed -->
- **πŸͺ€ Tripwires:**
  - [tripwire_1] <!-- Risk condition β†’ Contingency action -->
  - [tripwire_2] <!-- Risk condition β†’ Contingency action -->
- **πŸ‘€ Reviews:**
  - **[review_date] <!-- YYYY-MM-DD --> - [review_type] <!-- weekly|milestone|retrospective -->:**
    - **Completion Rate:** [completion_rate] <!-- Percentage complete (e.g., 75%) -->
    - **What went well:** [achievements] <!-- Specific wins and successes -->
    - **Challenges faced:** [challenges] <!-- Obstacles and their impact level -->
    - **Lessons learned:** [lessons_learned] <!-- Key insights for future work -->
    - **Action plan:** [action_plan] <!-- Next steps with owners and deadlines -->

Strategy & Planning: OKR

<!--
template_type: okr
project: [project_name]
status: [planning|active|completed]
-->

# OKR: [okr_name] <!-- Short, descriptive name for this OKR -->

Objective:

- [objective] <!-- Clear statement of what is to be achieved -->

Key Results:

- [ ] kr_1: [kr_1_description] <!-- Measurable outcome -->
  - success_criteria: [success_criteria_1] <!-- Metric or condition that denotes success -->
  - owner: [owner_1] <!-- Person responsible for this KR -->
- [ ] kr_2: [kr_2_description] <!-- Measurable outcome -->
  - success_criteria: [success_criteria_2] <!-- Metric or condition that denotes success -->
  - owner: [owner_2] <!-- Person responsible for this KR -->

Review Date:

- [review_date] <!-- YYYY-MM-DD format -->

Context & Dependencies:

- related_items: [related_items] <!-- Links or references to related work -->
- dependencies: [dependencies] <!-- What must be completed before this OKR can succeed -->

Notes:

- [notes] <!-- Optional additional context or instructions -->

Strategy & Planning: Roadmap

<!--
template_type: roadmap
project: [project_name]
status: [planning|active|completed]
priority: [high|medium|low]
-->

# πŸ›£οΈ Roadmap: [roadmap_name] <!-- Clear, descriptive name for this roadmap -->

- **πŸ“† Timeframe:**
  - [start_date] <!-- YYYY-MM-DD format --> to [end_date] <!-- YYYY-MM-DD format -->
- **πŸ”‘ Key Initiatives:**
  - **Initiative 1:**
    - [initiative_1_description] <!-- Description of the initiative -->
    - [initiative_1_timeline] <!-- Timeline or duration -->
  - **Initiative 2:**
    - [initiative_2_description] <!-- Description of the initiative -->
    - [initiative_2_timeline] <!-- Timeline or duration -->
- **πŸ”οΈ Milestones:**
  - [milestone_list] <!-- List of major milestones with dates -->

Strategy & Planning: Business Goal

<!--
template_type: business_goal
project: [project_name]
status: [draft|active|achieved|deprecated]
priority: [high|medium|low]
-->

# 🎯 Business Goal: [business_goal_name] <!-- Clear, descriptive name for this business goal -->

- **πŸ“Œ Business goal name:**
  - [business_goal_name] <!-- Concise name, e.g., "Minimize Equipment Downtime" -->
- **🎯 Objective statement:**
  - [objective_statement] <!-- Clear, measurable outcome the goal aims to achieve -->
- **πŸ“Š Supporting metrics:**
  - [supporting_metrics] <!-- Key Performance Indicators, e.g., MTTR, MTBF, revenue targets -->
- **πŸ” Strategic importance:**
  - [strategic_importance] <!-- Explanation of why this goal matters for the business -->
- **πŸ“† Target date:**
  - [target_date] <!-- YYYY-MM-DD format -->
- **πŸ“† Review date:**
  - [review_date] <!-- YYYY-MM-DD format -->
- **πŸ”— Dependencies:**
  - [dependencies] <!-- Related factors, systems, or other business goals that impact this goal -->

Strategy & Planning: Business Process

<!--
template_type: business_process
domain: [domain_area]
status: [analysis|design|implementation|review]
priority: [high|medium|low]
-->

# πŸ”„ Business Process: [process_name] <!-- Clear, descriptive name for this business process -->

- **πŸ“Œ Process Name:**
  - [process_name] <!-- Unique identifier for the process -->
- **πŸ“ Stages:**
  - [stage_1] <!-- First key step in the process -->
  - [stage_2] <!-- Second key step in the process -->
  - [stage_3] <!-- Third key step in the process -->
- **😞 Pain Points:**
  - [pain_point_1] <!-- Specific challenge or bottleneck -->
  - [pain_point_2] <!-- Another challenge or inefficiency -->
  - [pain_point_3] <!-- Additional problem area -->
- **πŸš€ Opportunities:**
  - [opportunity_1] <!-- Area for improvement or optimization -->
  - [opportunity_2] <!-- Another enhancement possibility -->
  - [opportunity_3] <!-- Additional improvement area -->
- **πŸ”„ Inputs / Triggers:**
  - [trigger_1] <!-- What initiates the process -->
  - [trigger_2] <!-- Alternative starting condition -->
- **βœ… Outputs / Results:**
  - [output_1] <!-- Primary expected outcome -->
  - [output_2] <!-- Secondary expected result -->
- **πŸ‘₯ Key Stakeholders:**
  - [stakeholder_1] <!-- Primary role involved -->
  - [stakeholder_2] <!-- Secondary role involved -->
  - [stakeholder_3] <!-- Additional involved party -->

Strategy & Planning: Governance Model

<!--
template_type: governance_model
organization: [organization_name]
status: [draft|active|under_review|archived]
priority: [high|medium|low]
-->

# πŸ›οΈ Governance Model: [governance_model_name] <!-- Clear, descriptive name for this governance model -->

- **🧠 Decision-Making Structure:**
  - [decision_maker_1] <!-- Primary decision-making authority -->
  - [decision_maker_2] <!-- Secondary decision-making role -->
  - [decision_maker_3] <!-- Additional decision-making participant -->
- **πŸ—£οΈ Policies:**
  - [policy_1] <!-- Key guiding policy or principle -->
  - [policy_2] <!-- Important governance policy -->
  - [policy_3] <!-- Additional guiding policy -->
- **πŸ•΅οΈβ€β™‚οΈ Roles & Responsibilities:**
  - [role_1] <!-- Primary governance role and responsibilities -->
  - [role_2] <!-- Secondary governance role and duties -->
  - [role_3] <!-- Additional governance role -->
- **🚲 Review Cycle:**
  - [review_frequency] <!-- How often governance is reviewed, e.g., quarterly, annually -->

Strategy & Planning: Stakeholder Map

# πŸ‘₯ Stakeholder Map

| Stakeholder  | Role   | Interest/Influence | Allocation (%) |
| ------------ | ------ | ------------------ | -------------- |
| [Name/Group] | [Role] | [High/Medium/Low]  | [Percentage]   |

Strategy & Planning: Strategy

<!--
template_type: strategy
organization: [organization_name]
status: [draft|active|under_review|archived]
priority: [high|medium|low]
-->

# πŸ—ΊοΈ Strategy: [strategy_name] <!-- Clear, descriptive name for this strategic plan -->

- **🌁 Vision, Future & Impact**
  - **Aspiration:** [aspiration_statement] <!-- A clear, inspiring statement of the future we aim to create -->
  - **Future Success:** [future_success_metrics] <!-- What measurable outcomes define success in our vision -->
  - **Impact on Stakeholders:** [stakeholder_impact] <!-- How does our vision benefit customers, employees, and the broader community -->
- **β›ͺ️ Purpose & Core Beliefs**
  - **Purpose:** [purpose_statement] <!-- Why do we exist? What impact do we want to make -->
  - **Core Values:** [core_values] <!-- Fundamental principles that guide our decisions and behavior -->
  - **Guiding Principles / Key Strategic Choices:** [guiding_principles] <!-- What strategic beliefs drive our actions -->
- **🎒 Strategic Themes**
  - **Theme 1:** [strategic_theme_1] <!-- A major focus area aligned with our vision -->
  - **Theme 2:** [strategic_theme_2] <!-- Another key area guiding our long-term direction -->
- **πŸ† Ambition & Goals**
  - **Short-Term:** [short_term_goals] <!-- What measurable goals do we aim to achieve soon? E.g. 1-3 years -->
  - **Long-Term:** [long_term_aspirations] <!-- What transformative aspirations guide us without current limitations? E.g. 5-10 years -->
- **πŸ“ Narrative & Differentiation**
  - **Innovation & Differentiation:** [innovation_differentiation] <!-- How do we create unique value and inspire change -->
  - **Story:** [organizational_story] <!-- Our journey, challenges, and visionβ€”focusing on the "why" and "what" rather than the "how" -->

Strategy & Planning: Key questions before starting the work

<!--
template_type: project_pre_work_questions
project: [project_name]
status: [planning|in_progress|completed]
priority: [high|medium|low]
-->

# πŸ€” Key Questions Before Starting the Work: [project_name] <!-- Clear, descriptive name for this project assessment -->

- **πŸ’Ž What is worth it?**
  - What are we certain we can actually achieve, both in terms of tasks and outcomes, given the constraints of reality? [achievability_assessment] <!-- Realistic assessment of what can be accomplished -->
  - From organisation's point of view: will all items return the investment? [organizational_roi] <!-- Expected return on investment for the organization -->
  - From our point of view: will all items be worth our time, budget and resources? [team_value_assessment] <!-- Assessment of value for the team -->
  - From users' point of view: will all items bring real value to users? [user_value_proposition] <!-- Clear statement of user value -->
  - Are we able to provide support and maintenance, and improve the work after the work is done? [post_launch_capabilities] <!-- Assessment of ongoing support capabilities -->
- **πŸ–ΌοΈ What are we doing?**
  - Is the goal understandable to all involved? [goal_clarity] <!-- Assessment of goal comprehension across stakeholders -->
  - Is the current plan and content accessible to all involved? [plan_accessibility] <!-- Evaluation of plan clarity and availability -->
  - Is the timeline and milestones clear to all involved? [timeline_clarity] <!-- Assessment of schedule understanding -->
- **πŸ’Ά What is the value of the outcome?**
  - Who are we creating value for? Who is the target audience? [target_audience] <!-- Clear definition of beneficiaries -->
  - What is the underlying critical need that we aim to address? [critical_need] <!-- Core problem or opportunity being addressed -->
  - How is the outcome going to differentiate from alternatives? Who or what are the direct and indirect competitors? [competitive_differentiation] <!-- Unique value proposition and competitive analysis -->

Strategy & Planning: Pitch

<!--
template_type: pitch
product: [product_name]
status: [draft|active|under_review|archived]
priority: [high|medium|low]
-->

# 🎯 Pitch: [product_service_name] <!-- Clear, descriptive name for this product or service -->

For **[target_audience]** <!-- Who is the target audience --> who need **[opportunity_pain]** <!-- What opportunity or pain point they have -->, **[product_service]** <!-- Name of the product or service --> provides **[solution]** <!-- What solution it provides -->. Unlike **[alternatives]** <!-- What are the alternatives --> it **[differentiators]** <!-- What makes it different and better -->.

Research: Contextual inquiry

<!--
template_type: contextual_inquiry
project: [project_name]
status: [planned|in_progress|completed]
priority: [high|medium|low]
-->

# πŸ” Contextual Inquiry: [inquiry_name] <!-- Clear, descriptive name for this contextual inquiry session -->

## 1. Session Information

- **πŸ—“οΈ Date & Time:** [session_date_time] <!-- YYYY-MM-DD HH:MM format -->
- **πŸ“ Location/Setting:** [location_setting] <!-- Description of where the session takes place -->
- **🎯 Objective:** [session_objective] <!-- Main focus of this inquiry session -->
- **🎯 Context:** [session_context] <!-- Main context, e.g. related project or design track -->

## 2. Participant Details

- **πŸ‘€ Participant Name:** [participant_name] <!-- Name or pseudonym for the participant -->
- **πŸ“‹ Role/Background:** [participant_role_background] <!-- User's role or relevant background information -->
- **πŸ” Contextual Factors:** [contextual_factors] <!-- Key factors like experience level, familiarity with the product, etc. -->

## 3. Environment & Setup

- **🏑 Environment Description:** [environment_description] <!-- Describe the physical and digital environment observed -->
- **πŸ’» Devices & Tools:** [devices_tools] <!-- List the devices, software, or tools used by the participant -->
- **πŸ”§ Setup/Configuration:** [setup_configuration] <!-- Notes on workspace setup or any configuration details -->

## 4. Observed Tasks & Behaviors

- **πŸ“ Tasks Overview:**
  - [task_1] <!-- First key task the participant is performing -->
  - [task_2] <!-- Second key task observed -->
  - [task_3] <!-- Additional task if applicable -->
- **⏱️ Task Duration & Sequence:**
  - [task_duration_sequence] <!-- Time taken per task or the order in which tasks are performed -->
- **πŸ” Behaviors & Interactions:**
  - [behaviors_interactions] <!-- Detailed observations of how the participant interacts with the system -->

## 5. User Feedback & Quotes

- **πŸ’¬ Direct Quotes:**
  - "[quote_1]" <!-- Record verbatim quotes that provide insight -->
  - "[quote_2]" <!-- Additional meaningful quote -->
- **πŸ™‚ Positive Feedback:**
  - [positive_feedback] <!-- What aspects of the experience did the participant like -->
- **😟 Pain Points/Frustrations:**
  - [pain_point_1] <!-- First issue, confusion, or challenge observed -->
  - [pain_point_2] <!-- Second pain point if applicable -->

## 6. Insights & Opportunities

- **πŸ’‘ Key Insights:**
  - [key_insight_1] <!-- Primary takeaway from the session -->
  - [key_insight_2] <!-- Additional important insight -->
- **πŸš€ Opportunities for Improvement:**
  - [opportunity_1] <!-- First potential improvement or new idea based on observations -->
  - [opportunity_2] <!-- Second improvement opportunity -->

## 7. Follow-Up Actions

- **πŸ”„ Next Steps:**
  - [next_step_1] <!-- First planned follow-up interview, test, or design adjustment -->
  - [next_step_2] <!-- Additional follow-up action -->
- **πŸ“Œ Additional Notes:**
  - [additional_notes] <!-- Any extra observations or context that might be useful later -->

Design & Problem Solving: Develop shared vision with triads

<!--
template_type: shared_vision_triads
project: [project_name]
status: [planning|workshop|completed]
priority: [high|medium|low]
-->

# πŸ“ Develop Shared Vision with Triads: [vision_session_name] <!-- Clear, descriptive name for this vision development session -->

<!-- Source: The User Experience Team of One. Leah Buley and Joe Natoli. 2nd edition, p.124. -->

- **🧠 Step 1: Describe the product/service**
  - [descriptive_words] <!-- Brainstorm words (10+) that describes the product or service -->
- **πŸ“ Step 2: Pick words in group of three**
  - [word_triad_1] <!-- First group of three words that put together describes the product -->
  - [word_triad_2] <!-- Second group of three words -->
  - [word_triad_3] <!-- Third group of three words -->
- **πŸ—£οΈ Step 3: For each group: Describe**
  - **Related nouns (5-10):** [related_nouns] <!-- What nouns do you think of when you see the words? (system objects) -->
  - **Related verbs (5-10):** [related_verbs] <!-- What verbs do you think of when you see the words? (system actions) -->
  - **Related adjectives (5-10):** [related_adjectives] <!-- What adjectives do you think of when you see the words? (system look, feel and behavior) -->
- **πŸ† Step 4: For each outcome: describe what you see**
  - **Experience vision:** [experience_vision] <!-- What kind of experience do you envision -->
  - **Important parts:** [important_parts] <!-- What would be the most important parts of the product/service -->
  - **How it works:** [how_it_works] <!-- How would the product/service work -->
  - **User feelings:** [user_feelings] <!-- How would users and customers feel about it -->

Design & Problem Solving: JTBD

<!--
template_type: job_to_be_done
project: [project_name]
status: [research|analysis|validated|implemented]
priority: [high|medium|low]
-->

# 🎯 Job to Be Done (JTBD): [jtbd_name] <!-- Clear, descriptive name for this job to be done -->

- **πŸ§β€β™‚οΈPerson:**
  - [person_description] <!-- Who is trying to accomplish this -->
- **πŸ‘· Job Statement:**
  - [job_statement] <!-- When I... I want to... so I can... -->
- **😣 Pain Points & Frictions:**
  - [ ] [pain_point_1] <!-- First specific issue or friction -->
  - [ ] [pain_point_2] <!-- Second issue or challenge -->
  - [ ] [pain_point_3] <!-- Additional pain point if applicable -->
- **πŸ† Success Criteria:**
  - [success_criteria] <!-- What success looks like -->
- **πŸ”Ή Existing Alternatives / Workarounds:**
  - [alternative_1] <!-- Current workaround or alternative solution -->
  - [alternative_2] <!-- Additional existing alternative -->
- **πŸ—οΈ Proposed Solution (if applicable):**
  - [proposed_solution] <!-- Brief description of suggested solution -->
- **❓ Open Questions / Risks:**
  - [question_risk_1] <!-- First uncertainty or blocker -->
  - [question_risk_2] <!-- Additional question or risk -->

Design & Problem Solving: JTBD hierarchy

<!--
template_type: jtbd_hierarchy
project: [project_name]
status: [research|analysis|validated|implemented]
priority: [high|medium|low]
-->

# 🎯 Job to Be Done (JTBD) Hierarchy: [jtbd_hierarchy_name] <!-- Clear, descriptive name for this JTBD hierarchy analysis -->

- **⬇️ Why:** [why_level_1] <!-- First level of why - deeper motivation -->
- **⬇️ Why:** [why_level_2] <!-- Second level of why - underlying reason -->
- **⬇️ Why:** [why_level_3] <!-- Third level of why - root motivation -->
- **⬇️ Why:** [why_level_4] <!-- Fourth level of why - fundamental driver -->
- **Job Statement:** [job_statement] <!-- When I... I want to... so I can... -->
- **⬆️ How:** [how_step_1] <!-- First concrete step to accomplish the job -->
- **⬆️ How:** [how_step_2] <!-- Second concrete step in the process -->
- **⬆️ How:** [how_step_3] <!-- Third concrete step or action -->
- **⬆️ How:** [how_step_4] <!-- Fourth concrete step to complete the job -->

## Example

- **⬇️ Why:** To jumpstart my morning energy
- **⬇️ Why:** To enjoy a comforting routine
- **⬇️ Why:** To carve out a quiet moment for myself
- **⬇️ Why:** To boost my productivity for the day
- **Job Statement:** When I start my day, I want to make myself a cup of coffee before leaving home.
- **⬆️ How:** Boil water using a kettle
- **⬆️ How:** Measure and grind coffee beans (or use a coffee pod)
- **⬆️ How:** Brew the coffee with a coffee maker
- **⬆️ How:** Pour the coffee into a mug

Design & Problem Solving: UX Issue

<!--
template_type: ux_issue
project: [project_name]
status: [reported|investigating|in_progress|resolved|closed]
priority: [critical|major|minor|trivial]
-->

# πŸ› UX Issue: [issue_name] <!-- Clear, descriptive name for this UX issue -->

- **πŸ“Œ Summary:**
  - [issue_summary] <!-- Short, clear description of the issue -->
- **πŸ”„ Description:**
  - [issue_description] <!-- Steps to reproduce, detailed description -->
- **⚠️ Expected vs. Actual:**
  - 😊 _Expected:_ [expected_behavior] <!-- What should happen -->
  - ❌ _Actual:_ [actual_behavior] <!-- What actually happens -->
- **🎨 UI Elements Affected:**
  - [affected_element_1] <!-- First component or screen affected -->
  - [affected_element_2] <!-- Second affected element -->
- **πŸ“· Screenshots / Recordings:**
  - ![Screenshot Title](filename.png) <!-- Reference to screenshot file -->
- **πŸ–₯️ Environment Details:**
  - Device: [device_type] <!-- Desktop/Mobile/Tablet -->
  - OS: [operating_system] <!-- Windows/macOS/Linux/iOS/Android -->
  - Browser: [browser_name] <!-- Chrome/Firefox/Safari/Edge/Other -->
- **πŸš€ Possible Solutions:**
  - [solution_suggestion_1] <!-- First potential solution -->
  - [solution_suggestion_2] <!-- Second potential solution -->
- **πŸͺ€ Severity & Impact:**
  - [severity_level] <!-- Critical/Major/Minor/Trivial -->
- **πŸ› οΈ Reported by:**
  - [reporter_email] <!-- Email of person who reported the issue -->
- **πŸ—“οΈ Date Reported:**
  - [report_date] <!-- YYYY-MM-DD format -->

Design & Problem Solving: HMW (How Might We)

<!--
template_type: hmw
project: [project_name]
status: [draft|active|completed]
priority: [high|medium|low]
-->

# πŸ€” How Might We (HMW): [hmw_name] <!-- Clear, descriptive name for this HMW session -->

- **🎯 Challenge Area:**
  - [challenge_area] <!-- Broad problem space -->
- **πŸ“ Observation / Insight:**
  - [observation_insight] <!-- What have we learned -->
- **πŸ’‘ How Might We:**
  - HMW [action] for [user] so that [desired_outcome]? <!-- How might we statement -->
- **πŸ› οΈ Constraints / Considerations:**
  - [constraints_considerations] <!-- Limitations or factors to consider -->
- **πŸ”Ή Related:**
  - [related_references] <!-- Links or references to related work -->

Design & Problem Solving: Problem Statement

<!--
template_type: problem_statement
project: [project_name]
status: [draft|defined|validated|solved]
priority: [high|medium|low]
-->

# πŸ›‘ Problem Statement: [problem_statement_name] <!-- Clear, descriptive name for this problem statement -->

- **🌍 Context:**
  - [context_background] <!-- Background of the issue -->
- **πŸ€• Problem:**
  - [problem_description] <!-- What is the issue and why it matters -->
- **πŸ‘€ Who is affected:**
  - [affected_users] <!-- User group or stakeholders -->
- **🎯 Goal / Desired Outcome:**
  - [desired_outcome] <!-- What should be achieved -->
- **⚠️ Pain Points / Challenges:**
  - [pain_point_1] <!-- First issue or challenge -->
  - [pain_point_2] <!-- Second issue or challenge -->
- **πŸ” Supporting Data / Insights:**
  - [supporting_data] <!-- Research, analytics, evidence -->
- **πŸš€ Potential Solutions (if applicable):**
  - [potential_solutions] <!-- Suggested approaches -->

Our [customer_segment] are [problem_what] because they [reason_why].  
If we solve this, it would impact [customer_segment] positively by [customer_benefit] and benefit our business by [business_benefit].

Design & Problem Solving: Double Diamond

<!--
template_type: double_diamond
project: [project_name]
status: [discover|define|develop|deliver]
priority: [high|medium|low]
-->

# πŸ”· Double Diamond: [double_diamond_name] <!-- Clear, descriptive name for this double diamond process -->

- **πŸ“… Date:**
  - [session_date] <!-- YYYY-MM-DD format -->
- **πŸ‘₯ Participants:**
  - [participant_list] <!-- List names/emails -->

## 1️⃣ Discover

- πŸ” **Problem Exploration:**
  - [problem_exploration] <!-- Understanding the challenge -->
- πŸ—£οΈ **User Research:**
  - [user_research] <!-- Key insights -->
- πŸ“Š **Data Analysis:**
  - [data_analysis] <!-- Findings -->
- ❓ **Challenges Identified:**
  - [challenge_1] <!-- First challenge -->
  - [challenge_2] <!-- Second challenge -->

## 2️⃣ Define

- 🎯 **Key Problem Statement:**
  - [problem_statement] <!-- Clear articulation -->
- 😣 **Pain Points:**
  - [pain_point_1] <!-- First pain point -->
  - [pain_point_2] <!-- Second pain point -->
- πŸ–ΌοΈ **Scope & Constraints:**
  - [scope_constraints] <!-- In/out of scope -->

## 3️⃣ Develop

- πŸ’‘ **Brainstorming Ideas:**
  - [idea_1] <!-- First idea -->
  - [idea_2] <!-- Second idea -->
- 🎨 **Wireframes / Mockups:**
  - [wireframes_mockups] <!-- Links or screenshots -->
- βš™οΈ **Prototype Testing:**
  - [prototype_testing] <!-- User feedback -->

## 4️⃣ Deliver

- πŸš€ **Final Solution:**
  - [final_solution] <!-- What was implemented -->
- πŸ“ˆ **Impact Measurement:**
  - [impact_measurement] <!-- Metrics & feedback -->
- πŸ”„ **Iterative Improvements:**
  - [iterative_improvements] <!-- Next steps -->

Design & Problem Solving: User Journey

<!--
template_type: user_journey
project: [project_name]
status: [draft|in_progress|validated|implemented]
priority: [high|medium|low]
-->

# πŸ›€οΈ User Journey: [user_journey_name] <!-- Clear, descriptive name for this user journey -->

- **πŸ“Œ Name:**
  - [journey_name] <!-- Journey name, e.g. "Resolving Equipment Downtime" -->
- **πŸ“ Stages:**
  - [journey_stages] <!-- Journey stages, e.g. "Detection β†’ Reporting β†’ Diagnostics β†’ Repair β†’ Validation" -->
- **🎯 User Goals:**
  - [user_goals] <!-- User goals, e.g. "Minimize downtime" -->
- **😞 Pain Points:**
  - [pain_points] <!-- Pain points, e.g. "Delayed part delivery" -->
- **πŸš€ Opportunities:**
  - [opportunities] <!-- Opportunities, e.g. "Real-time data aggregation" -->
- **πŸ”„ Randomness / Variability:**
  - [variability_factors] <!-- Variability factors, e.g. "Inconsistent IoT sensor data" -->
- **πŸ“‚ Mapped Business Process:**
  - [mapped_process] <!-- Related business process, e.g. "Equipment Maintenance Process" -->
- **πŸ“Š Key Metrics:**
  - [key_metrics] <!-- Key metrics, e.g. "Reduce Mean Time to Repair" -->

Design & Problem Solving: Persona

<!--
template_type: persona
project: [project_name]
status: [draft|validated|active|archived]
priority: [high|medium|low]
-->

# πŸ‘€ Persona: [persona_name] <!-- Clear, descriptive name for this persona -->

- **πŸ“› Name:** [persona_name] <!-- Persona name, e.g. "Jane Doe" -->
- **πŸ’Ό Role:** [persona_role] <!-- Persona role, e.g. "Maintenance Technician" -->
- **πŸ–ΌοΈ Picture:**
  - [persona_image] <!-- Photo or illustration -->
- **🎯 Focus:**
  - [key_focus] <!-- Key interaction aspect -->
- **πŸ“ Notes:**
  - [persona_notes] <!-- Motivations, goals, challenges -->

Design & Problem Solving: Contextual Use Scenario

<!--
template_type: contextual_use_scenario
project: [project_name]
status: [draft|validated|implemented|archived]
priority: [high|medium|low]
-->

# 🎭 Contextual Use Scenario: [scenario_name] <!-- Clear, descriptive name for this scenario -->

- **πŸ†” ID:**
  - [scenario_id] <!-- Unique ID, e.g., "#001" -->
- **πŸ“‚ Group:**
  - [scenario_group] <!-- Scenario group, e.g., "Diagnostics" -->
- **πŸ‘€ Persona:**
  - [related_persona] <!-- Related persona, e.g., "John Smith" -->
- **πŸ“– Description:**
  - [scenario_description] <!-- Narrative explanation -->
- **🎯 User Goal:**
  - [user_goal] <!-- What the user is trying to achieve -->
- **πŸ’‘ Design Hypothesis:**
  - [design_hypothesis] <!-- Early design ideas -->

Design & Problem Solving: User Story

<!--
template_type: lessons_learned
project: [project_name]
status: [draft|reviewed|finalized|archived]
priority: [high|medium|low]
-->

# πŸ“ User Story: [story_name] <!-- Clear, descriptive name for this user story -->

- **πŸ‘€ Role:**
  - [user_role] <!-- User or stakeholder, e.g. "Maintenance Technician" -->
- **🎯 Action / Need:**
  - [user_action] <!-- What the user wants to do -->
- **πŸ” Purpose / Benefit:**
  - [user_benefit] <!-- Why it's needed -->
- **πŸ“Œ Full User Story:**
  - "As a [role], I want to [action] so that [benefit]." <!-- Complete user story -->
- **πŸ”— Dependencies:**
  - [story_dependencies] <!-- Tools or conditions required -->
- **πŸ† Outcome:**
  - [success_criteria] <!-- Success criteria -->

Design & Problem Solving: Use Case

<!--
template_type: use_case
project: [project_name]
status: [draft|defined|validated|implemented]
priority: [high|medium|low]
-->

# πŸ“‘ Use Case: [use_case_name] <!-- Clear, descriptive name for this use case -->

- **πŸ“Œ Use Case Name:** [use_case_name] <!-- Use case name, e.g. "Retrieve Diagnostic Error Codes" -->
- **🎯 Objective:**
  - [use_case_objective] <!-- Purpose of the interaction -->
- **πŸ“ Preconditions:**
  - [preconditions] <!-- What must be true -->
- **πŸ”„ Steps:**
  1. [step_1] <!-- First step -->
  2. [step_2] <!-- Second step -->
- **πŸ† Outcome:**
  - [expected_outcome] <!-- Expected result -->
- **😞 Pain Points:**
  - [pain_points] <!-- Potential challenges -->
- **πŸš€ Opportunities:**
  - [opportunities] <!-- Improvements -->
- **πŸ”— Dependencies:**
  - [dependencies] <!-- Required tools or systems -->

Design & Problem Solving: Design Version Notes

# 🎨 Design Version Notes

- **🌱 Version:** [e.g., v1.0]
- **πŸ“† Date:** [YYYY-MM-DD]
- **πŸ‘€ Author:** [email]
- **πŸ‘€ Overview:** [A brief description of what this design version covers and its focus.]
- **πŸ“š Context:** [Background information and the reasons for this versionβ€”what challenges or opportunities led to this update.]
- **🌟 What is new?:**
  - **Main reason for new version:** [Describe how this version improves on past designs.]
  - **Change 1:** [Description of the change]
  - **Change 2:** [Description of the change]
- **πŸ›‚ Known issues:**
  - **Issue 1:** [Describe any problems or areas needing attention]
  - **Issue 2:** [Describe any problems or areas needing attention]
- **πŸ’†β€β™‚οΈ Concerns and uncertainties:**
  - [Outline any reservations or uncertainties regarding this design version.]
- **πŸ“£ Feedback Requested From:**
  - [List the stakeholders or team members expected to review this version.]
- **πŸ”Ž Focus Areas for Feedback:**
  - [ ] Interaction design
  - [ ] Visual aesthetics
  - [ ] Usability
  - [ ] Alignment with brand guidelines / design system
  - [ ] Functionality
- **πŸ“’ How to Provide Feedback:**
  - [e.g., via comments in the document, email, or scheduled review meeting.]
- **πŸ—“οΈ Planned Revisions:**
  - [Outline any planned changes or iterations based on the feedback.]
- **πŸ›£οΈ Next Version Roadmap:**
  - [If known, describe what’s planned for the next iteration.]
- **πŸ“ Notes:**
  - [Any extra information, references, or clarifications that might help understand this version.]

Design & Problem Solving: SFDIPOT

<!--
template_type: sfdipot
project: [project_name]
status: [analysis|in_progress|completed]
priority: [high|medium|low]
-->

# πŸŒ‰ SFDIPOT Template: [sfdipot_analysis_name] <!-- Clear, descriptive name for this SFDIPOT analysis -->

## πŸ—οΈ Structure

- **What is the application's architecture?**
  - [architecture_description] <!-- Description of application architecture -->
- **What technologies are used?**
  - [technologies_used] <!-- List of technologies, e.g., databases, APIs, authentication methods -->
- **Are there dependencies on third-party services?**
  - [third_party_dependencies] <!-- Dependencies on external services -->

## βš™οΈ Function

- **What are the key functionalities of the application?**
  - [key_functionalities] <!-- List of key functionalities -->
- **List critical user actions and system processes.**
  - [critical_actions] <!-- Critical user actions and system processes -->
- **Are there hidden or less obvious functions?**
  - [hidden_functions] <!-- Less obvious or hidden functions -->

## πŸ—„οΈ Data

- **What types of data does the application handle?**
  - [data_types] <!-- Types of data handled -->
- **How is data stored, processed, and transmitted?**
  - [data_handling] <!-- Data storage, processing, and transmission methods -->
- **Are there validation checks for inputs?**
  - [validation_checks] <!-- Input validation methods -->

## πŸ”— Interfaces

- **What interfaces does the application have?**
  - [application_interfaces] <!-- Interfaces like UI, API, CLI, third-party integrations -->
- **Are there import/export features?**
  - [import_export_features] <!-- Import/export capabilities -->
- **Are error messages and logs useful and clear?**
  - [error_handling] <!-- Error message and logging quality -->

## πŸ’» Platform

- **What platforms does the application support?**
  - [supported_platforms] <!-- Supported OS, browsers, mobile devices -->
- **Are there platform-specific behaviors or issues?**
  - [platform_behaviors] <!-- Platform-specific behaviors or issues -->
- **What are the system requirements?**
  - [system_requirements] <!-- System requirements -->

## πŸ” Operations

- **Who will use and maintain the system?**
  - [system_users] <!-- Users and maintainers of the system -->
- **Are there security, logging, or monitoring considerations?**
  - [security_considerations] <!-- Security, logging, or monitoring considerations -->
- **What are the backup and recovery strategies?**
  - [backup_recovery] <!-- Backup and recovery strategies -->

## ⏳ Time

- **Are there time-dependent functions?**
  - [time_dependent_functions] <!-- Time-dependent functions like scheduling, time zones, expiration dates -->
- **How does the system handle date/time changes (e.g., leap years, daylight saving)?**
  - [datetime_handling] <!-- Date/time change handling -->
- **Are there performance considerations under peak loads?**
  - [performance_considerations] <!-- Performance considerations under peak loads -->

Design & Problem Solving: UX KPI Discovery

<!--
template_type: ux_kpi_discovery
project: [project_name]
status: [discovery|analysis|defined|implemented]
priority: [high|medium|low]
-->

# πŸ” UX KPI Discovery: [kpi_discovery_name] <!-- Clear, descriptive name for this UX KPI discovery session -->

## 1. 🎯 Define UX Objectives & Goals

- **πŸ“Œ Objective Statement:**
  - [objective_statement] <!-- Describe the overall UX vision or mission for your product/service -->
- **⚠️ Key UX Challenges:**
  - [key_ux_challenges] <!-- List the main challenges users face -->
- **πŸ† Desired Outcomes:**
  - [desired_outcomes] <!-- What improvements or successes are you aiming for? -->

## 2. πŸ—ΊοΈ Analyze the User Journey & Critical Touchpoints

- **πŸ” User Journey Mapping:**
  - [user_journey_mapping] <!-- Identify key steps and interactions in the user journey -->
- **🎯 Critical Moments:**
  - [critical_moments] <!-- Which touchpoints have the most significant impact on user satisfaction? -->

## 3. πŸ’‘ Brainstorm Potential Metrics

- **πŸ”Ž What Does Success Look Like?**
  - [success_indicators] <!-- Brainstorm qualitative and quantitative indicators of success -->
- **πŸ“Š Potential KPI Ideas:**
  - [ ] **πŸ“Œ KPI Idea 1:** [kpi_idea_1] <!-- Description and rationale -->
  - [ ] **πŸ“Œ KPI Idea 2:** [kpi_idea_2] <!-- Description and rationale -->
- **πŸ’¬ User Feedback Integration:**
  - [feedback_integration] <!-- How can user feedback inform which metrics are most meaningful? -->

## 4. πŸ“‘ Data Availability & Measurement Feasibility

- **πŸ“‚ Data Sources:**
  - [data_sources] <!-- List available data sources such as analytics tools, surveys, or usability tests -->
- **πŸ› οΈ Measurement Capabilities:**
  - [measurement_capabilities] <!-- Which metrics are currently tracked and what new data could be collected? -->
- **🚧 Feasibility Considerations:**
  - [feasibility_considerations] <!-- Discuss any limitations or technical constraints that may affect measurement -->

## 5. πŸŽ›οΈ Define Selection Criteria for KPIs

- **🎯 Relevance:**
  - [relevance_criteria] <!-- How directly does the potential KPI address the UX objectives? -->
- **πŸ“ˆ Actionability:**
  - [actionability_criteria] <!-- Will this KPI drive insights that lead to actionable improvements? -->
- **πŸ“Œ Simplicity & Clarity:**
  - [clarity_criteria] <!-- Is the KPI easy to understand and communicate across teams? -->
- **⏳ Timeliness:**
  - [timeliness_criteria] <!-- How frequently can this KPI be measured and reviewed? -->

## 6. πŸš€ Prioritize & Refine KPIs

- **πŸ“Œ Evaluation of Potential KPIs:**
  - [kpi_evaluation] <!-- Discuss or rate each KPI idea based on the criteria above -->
- **πŸ“Š Final Selection:**
  - [final_kpi_selection] <!-- List the KPIs that best align with your UX objectives -->
- **πŸ”„ Next Steps for Implementation:**
  - [implementation_steps] <!-- Outline the plan for tracking, reviewing, and refining these KPIs over time -->

## 7. πŸ“ Additional Notes & Insights

- **πŸ’‘ Insights & Observations:**
  - [insights_observations] <!-- Record any extra insights or discoveries from the KPI exploration process -->
- **πŸ“œ Action Items:**
  - [action_items] <!-- Assign responsibilities for further research or implementation -->

Creative Thinking: Reverse Brainstorm

<!--
template_type: reverse_brainstorm
project: [project_name]
status: [planning|in_progress|completed]
priority: [high|medium|low]
-->

# πŸ”„ Reverse Brainstorm: [reverse_brainstorm_name] <!-- Clear, descriptive name for this reverse brainstorm session -->

- **🎯 Problem Statement:**
  - [problem_statement] <!-- Describe the challenge or issue to address -->
- **🚫 Negative Ideation:**
  - [negative_ideation] <!-- List ideas on how to worsen the problem -->
- **β†ͺ️ Reversal Strategies:**
  - [reversal_strategies] <!-- For each negative idea, explain how doing the opposite could offer a solution -->
- **πŸ’‘ Potential Solutions:**
  - [potential_solutions] <!-- Brainstorm actionable solutions based on the reversed ideas -->
- **πŸ“Š Evaluation:**
  - [solution_evaluation] <!-- Assess feasibility, impact, and potential risks of the solutions -->
- **πŸͺœ Next Steps:**
  - [next_steps] <!-- Define action items, assign responsibilities, and set deadlines -->

Creative Thinking: Metaphoric Thinking

<!--
template_type: metaphoric_thinking
project: [project_name]
status: [exploration|analysis|insights_captured]
priority: [high|medium|low]
-->

# 🎨 Metaphoric Thinking: [metaphoric_thinking_name] <!-- Clear, descriptive name for this metaphoric thinking session -->

- **πŸ“ Concept / Challenge:**
  - [concept_challenge] <!-- Describe the idea or problem to explore -->
- **πŸ” Selected Metaphor:**
  - [selected_metaphor] <!-- Choose a metaphor that represents the situation, e.g., "a garden in need of nurturing" -->
- **πŸ“– Metaphor Breakdown:**
  - **Components:** [metaphor_components] <!-- List elements of the metaphor and their real-life counterparts -->
  - **Mapping:** [metaphor_mapping] <!-- Explain how the metaphor relates to the actual challenge -->
- **πŸ’‘ Insights & Implications:**
  - [insights_implications] <!-- Highlight new perspectives and insights derived from the metaphor -->
- **βš™οΈ Action Items:**
  - [action_items] <!-- Outline steps inspired by these insights to address the challenge -->

Comms and docs: Note-taking framework C-Q-E/I/D-T

<!--
template_type: note_taking_cqeidt
project: [project_name]
status: [active|completed|archived]
priority: [high|medium|low]
-->

# πŸ–ΌοΈ Note-taking framework C-Q-E/I/D-T: [note_session_name] <!-- Clear, descriptive name for this note-taking session -->

- 🍽️ Context:
  - [context_information] <!-- Background information, general statements, or foundational details that set the stage -->
- πŸ™‹β€β™‚οΈQuestions:
  - [key_questions] <!-- Key questions that arise from the context or that need to be explored -->
- πŸ§‘β€πŸ”¬Evidence / Ideas / Discussion:
  - [evidence_ideas_discussion] <!-- Facts, insights, arguments, discussion that help answer the questions or takes the topic further -->
- πŸ›«Takeaways
  - [final_takeaways] <!-- The final takeaway, summary, or conclusion -->

Comms and docs: Communication Plan

<!--
template_type: communication_plan
project: [project_name]
status: [draft|active|completed]
priority: [high|medium|low]
-->

# πŸ“’ Communication Plan: [communication_plan_name] <!-- Clear, descriptive name for this communication plan -->

- **🎯 Objective:**
  - [communication_objective] <!-- Purpose of the communication plan -->
- **πŸ‘₯ Audience:**
  - [target_audience] <!-- List stakeholder groups -->
- **πŸ“Ί Channels:**
  - [communication_channels] <!-- Communication channels, e.g., email, meetings, Slack, Teams, etc. -->
- **πŸ”‰ Frequency:**
  - [communication_frequency] <!-- How often communications occur -->
- **πŸ‘¨β€πŸ’Ό Responsible:**
  - [responsible_person] <!-- Responsible person's email -->

Comms and docs: Meeting Memo

<!--
template_type: meeting_memo
project: [project_name]
status: [draft|finalized|archived]
priority: [high|medium|low]
-->

# πŸ“… Meeting Memo: [meeting_memo_name] <!-- Clear, descriptive name for this meeting memo -->

- **πŸ—“οΈ Date/Time:**
  - [meeting_date_time] <!-- YYYY-MM-DD HH:MM-HH:MM format -->
- **πŸ“ Location / Link:**
  - [meeting_location_link] <!-- Meeting room or video call link -->
- **πŸ‘₯ Attendees:**
  - [participant_list] <!-- List names/emails -->
- **🎯 Agenda:**
  1. [agenda_topic_1] <!-- First agenda topic -->
  2. [agenda_topic_2] <!-- Second agenda topic -->
- **πŸ“Œ Key Notes & Discussions:**
  - πŸ“ [key_point] <!-- Key point discussed -->
  - ❓ [question_raised] <!-- Question raised -->
- **🏒 Decisions Made:**
  - [decision_1] <!-- First decision made -->
  - [decision_2] <!-- Second decision made -->
- **πŸš€ APs:**
  - [ ] [action_owner] [action_description] <!-- Action item with owner -->
- **πŸ‘Ÿ Next:**
  - [next_steps] <!-- Next steps or follow-up -->
- **πŸ“‚ Attachments & References:**
  - [attachments_references] <!-- Link or file attachment -->

Comms and docs: Meeting Agenda

<!--
template_type: meeting_agenda
project: [project_name]
status: [draft|final|completed]
priority: [high|medium|low]
-->

# πŸ—’οΈ Meeting Agenda: [meeting_agenda_name] <!-- Clear, descriptive name for this meeting agenda -->

- **πŸ—“οΈ Date/Time:**
  - [meeting_date_time] <!-- YYYY-MM-DD HH:MM format -->
- **πŸ“ Location / Link:**
  - [meeting_location_link] <!-- Meeting room or video call link -->
- **🎯 Agenda:**
  1. [agenda_topic_1] <!-- First agenda topic -->
  2. [agenda_topic_2] <!-- Second agenda topic -->
- **🍝 Expected Outcomes:**
  - [expected_outcomes] <!-- What is to be achieved -->

Comms and docs: Decision Record

<!--
template_type: decision_record
project: [project_name]
status: [draft|proposed|accepted|deprecated]
priority: [high|medium|low]
-->

# πŸ“œ Decision Record: [decision_record_name] <!-- Clear, descriptive name for this decision record -->

- **πŸ†” ID:** [decision_id] <!-- Unique ID -->
- **πŸ“… Date:** [decision_date] <!-- YYYY-MM-DD format -->
- **πŸ‘€ Author(s):** [author_email] <!-- Author email -->
- **πŸ“Œ Status:** [decision_status] <!-- Draft/Proposed/Accepted/Deprecated -->
- **πŸ—οΈ Context:** [decision_context] <!-- Problem and constraints -->
- **πŸ’‘ Decision:** [chosen_decision] <!-- Chosen solution and rationale -->
- ## **πŸ”„ Alternatives**
  1. **[alternative_1]** – [alternative_1_pros_cons] <!-- Pros/Cons of first alternative -->
  2. **[alternative_2]** – [alternative_2_pros_cons] <!-- Pros/Cons of second alternative -->
- **⚠️ Consequences:** [decision_consequences] <!-- Implications of the decision -->
- **πŸš€ Next Steps**
  - [follow_up_action_1] [review_date_1] <!-- First follow-up action and review date -->
  - [follow_up_action_2] [review_date_2] <!-- Second follow-up action and review date -->

Comms and docs: Pros and Cons

# πŸ‘ Pros and πŸ‘Ž Cons

- **🎯 Topic / Decision:**
  - [What is being evaluated]
- **πŸ“… Date:**
  - [eval_date] <!-- YYYY-MM-DD HH:MM format -->
- **πŸ‘€ Evaluated by:**
  - [email]

## πŸ‘ Pros

| Advantage | Explanation           |
| --------- | --------------------- |
| [Pro 1]   | [Why it’s beneficial] |
| [Pro 2]   | [How it adds value]   |

## πŸ‘Ž Cons

| Disadvantage | Explanation           |
| ------------ | --------------------- |
| [Con 1]      | [Why it’s a drawback] |
| [Con 2]      | [Potential risks]     |

## 🏁 Final Thoughts

[Summary of key takeaways]

Comms and docs: Conflict

# βš–οΈ Conflict: [Conflict Name]

- **πŸ“Œ Summary:**
  - [Brief explanation]
- **πŸ“ Context:**
  - [Background leading to the conflict]
- **πŸ‘₯ Involved Parties:**
  | Role | Name | Perspective |
  | ------- | -------- | ------------------------- |
  | [Role] | [Name] | [Viewpoint or concern] |
- **🎯 Key Issues:**
  - **Issue 1:** [First point of contention]
  - **Issue 2:** [Second point]
- **πŸ™… Points of Disagreement:**
  - πŸ“· **Perspective 1:** [One side’s stance]
  - πŸ“· **Perspective 2:** [Opposing stance]
- **πŸ“Š Impact:**
  - [How it affects the project/team]
- **πŸ› οΈ Constraints & External Factors:**
  - [Influencing factors]
- **πŸ”„ Attempts to Address:**
  - [Mitigation steps]
- **🚧 Barriers to Resolution:**
  - [Factors preventing resolution]
- **⏳ Urgency:**
  - [Time constraints]
- **πŸ“‚ Additional Notes:**
  - [Extra context]

Comms and docs: Assumption

<!--
template_type: assumption
project: [project_name]
status: [identified|validated|invalidated|archived]
priority: [high|medium|low]
-->

# πŸ” Assumption: [assumption_name] <!-- Clear, descriptive name for this assumption -->

- **πŸ“ Statement:**
  - "[assumption_statement]" <!-- Exact quote or summary -->
- **πŸ’‘ Inferred Assumption(s):**
  - [ ] **Assumption:** [inferred_assumption] <!-- Describe the underlying assumption implied by the statement -->
  - [ ] **βž• Additional Assumption (if any):** [additional_assumption] <!-- Describe any extra assumption -->
- **πŸ”‘ Key Phrases:**
  - [key_phrases] <!-- List phrases that suggest the assumption -->
- **⚠️ Potential Impact if False:**
  - [impact_if_false] <!-- Describe risks or outcomes if this assumption does not hold -->
- **πŸ€” Follow-Up / Clarification:**
  - **❓ Question:** [clarification_question] <!-- E.g., "Can you explain what data supports this view?" -->
  - **πŸ‘¨β€πŸš’ Action Item:** [action_item] <!-- Responsible person and due date, if applicable -->

Execution & Management: Track

<!--
template_type: track
project: [project_name]
status: [not_started|in_progress|completed|pending|skipped|postponed]
priority: [high|medium|low]
-->

# πŸš€ Track: [track_name] <!-- Clear, descriptive name for this track -->

- **πŸ› οΈ Current Status:**
  - [current_status] <!-- Not started | In Progress | Completed | Pending | Skipped | Postponed -->
- **πŸ“Œ Description:**
  - [track_description] <!-- Overview of the track -->
- **🎯 Goals & Objectives:**
  - [track_objectives] <!-- What the track aims to achieve -->
- **πŸ“† Timeline:**
  - Start: [start_date] <!-- YYYY-MM-DD format -->
  - Estimated Completion: [completion_date] <!-- YYYY-MM-DD format -->
- **πŸ“‚ Key Deliverables:**
  - [ ] **[deliverable_1]** – Due: [deliverable_1_date] <!-- YYYY-MM-DD format -->
  - [ ] **[deliverable_2]** – Due: [deliverable_2_date] <!-- YYYY-MM-DD format -->
- **πŸ”— Dependencies:**
  - [track_dependencies] <!-- Dependencies or links -->
  - [raci_link] <!-- Link to RACI -->
- **⚠️ Risks & Challenges:**
  - [risks_challenges] <!-- Potential blockers -->
- **πŸ“Š Success Metrics:**
  - [success_metrics] <!-- How success is measured -->

Execution & Management: RACI

<!--
template_type: raci
project: [project_name]
status: [draft|active|completed|archived]
priority: [high|medium|low]
-->

# πŸ—οΈ RACI: [raci_name] <!-- Clear, descriptive name for this RACI matrix -->

**πŸ“Œ Description:** [raci_description] <!-- Overview of roles and responsibilities -->

## πŸ”Ή RACI Definitions

| Letter | Meaning     | Description              |
| ------ | ----------- | ------------------------ |
| **R**  | Responsible | Does the work            |
| **A**  | Accountable | Makes the final decision |
| **C**  | Consulted   | Provides input           |
| **I**  | Informed    | Kept updated             |

## πŸ“Š Roles & Responsibilities

| Task / Deliverable | Responsible (R) | Accountable (A) | Consulted (C) | Informed (I) |
| ------------------ | --------------- | --------------- | ------------- | ------------ |
| **[Task 1]**       | [Name/Role]     | [Name/Role]     | [Name/Role]   | [Name/Role]  |
| **[Task 2]**       | [Name/Role]     | [Name/Role]     | [Name/Role]   | [Name/Role]  |

Execution & Management: Work Breakdown Structure (WBS)

<!--
template_type: wbs
project: [project_name]
status: [planning|active|completed|archived]
priority: [high|medium|low]
-->

# πŸ“‹ Work Breakdown Structure (WBS): [wbs_name] <!-- Clear, descriptive name for this WBS -->

- **🏷️ Project Name:**
  - [project_name] <!-- Project name -->
- **πŸ“‹ Tasks Breakdown:**
  1. **Phase 1:**
  - Task 1: [phase_1_task_1] <!-- Task description -->
  - Task 2: [phase_1_task_2] <!-- Task description -->
  2. **Phase 2:**
  - Task 1: [phase_2_task_1] <!-- Task description -->
  - Task 2: [phase_2_task_2] <!-- Task description -->
- **🏁 Milestones:**
  - [key_milestones] <!-- Key milestones -->

Execution & Management: Risk Register

<!--
template_type: risk_register
project: [project_name]
status: [active|under_review|closed]
priority: [high|medium|low]
-->

# πŸš€ Risk Register: [risk_register_name] <!-- Clear, descriptive name for this risk register -->

| Risk ID | Description   | Impact (High/Med/Low) | Probability (High/Med/Low) | Mitigation Plan       | Owner       |
| ------- | ------------- | --------------------- | -------------------------- | --------------------- | ----------- |
| R-001   | [Risk Detail] | High                  | Medium                     | [Mitigation strategy] | [Name/Team] |
| R-002   | [Risk Detail] | Low                   | High                       | [Mitigation strategy] | [Name/Team] |

- **πŸ” Risk Monitoring Plan:**
  - [risk_monitoring_plan] <!-- How risks will be reviewed -->

Execution & Management: Change Request

<!--
template_type: change_request
project: [project_name]
status: [pending|approved|rejected|implemented]
priority: [high|medium|low]
-->

# ⚑ Change Request: [change_request_name] <!-- Clear, descriptive name for this change request -->

- **πŸ“… Date:**
  - [request_date] <!-- YYYY-MM-DD format -->
- **πŸ“Œ Change Title:**
  - [change_title] <!-- Brief description -->
- **🎯 Reason for Change:**
  - [change_reason] <!-- Why the change is needed -->
- **πŸ“Š Impact Assessment:**
  - Timeline: [timeline_impact] <!-- Increase/Decrease/No impact -->
  - Budget: [budget_impact] <!-- Increase/Decrease/No impact -->
  - Resources: [resource_impact] <!-- More/Less/Same -->
- **πŸ“ Approval Status:**
  - [approval_status] <!-- Pending | Approved | Rejected -->
- **πŸ‘₯ Stakeholders Notified:**
  - [notified_stakeholders] <!-- List affected teams -->
- **πŸͺœ Next Steps:**
  - [next_steps] <!-- Implementation plan if approved -->

Execution & Management: Retrospective Summary

<!--
template_type: retrospective_summary
project: [project_name]
status: [conducted|documented|actions_assigned]
priority: [high|medium|low]
-->

# πŸ”„ Retrospective Summary: [retrospective_name] <!-- Clear, descriptive name for this retrospective -->

- **πŸ“š Topic/Scope:**
  - [retrospective_scope] <!-- Time period, sprint, or project -->
- **πŸ“… Date:**
  - [retrospective_date] <!-- YYYY-MM-DD format -->
- **πŸ‘ What Went Well:**
  - [successes] <!-- Key successes -->
- **πŸšΆβ€β™‚οΈβ€βž‘οΈ Challenges Faced:**
  - [challenges] <!-- Obstacles encountered -->
- **πŸ”¨ Actionable Improvements:**
  - [improvements] <!-- List improvements and owners -->
- **πŸͺœ Next Steps:**
  - [next_actions] <!-- Agreed actions for the next period -->

Execution & Management: Feature Brief

<!--
template_type: feature_brief
project: [project_name]
status: [concept|planning|in_development|completed]
priority: [high|medium|low]
-->

# 🌟 Feature Brief: [feature_name] <!-- Clear, descriptive name for this feature -->

- **πŸ“ Summary:**
  - [feature_summary] <!-- Brief overview of the feature -->
- **🎯 Purpose:**
  - [feature_purpose] <!-- Why this feature is needed -->
- **πŸ’₯ Impact:**
  - [feature_impact] <!-- Expected benefits -->
- **πŸ”‘ Key Components:**
  - [component_1] <!-- First component -->
  - [component_2] <!-- Second component -->

Execution & Management: Acceptance Criteria

<!--
template_type: acceptance_criteria
project: [project_name]
status: [draft|reviewed|approved|validated]
priority: [high|medium|low]
-->

# πŸ‘Œ Acceptance Criteria: [acceptance_criteria_name] <!-- Clear, descriptive name for this acceptance criteria -->

- **πŸš€ Feature/Task:**
  - [feature_task_name] <!-- Feature or task name -->
- **πŸ“‹ Criteria:**
  - [ ] Criterion 1: [criterion_1] <!-- First criterion description -->
  - [ ] Criterion 2: [criterion_2] <!-- Second criterion description -->
- **πŸ‘Œ Validation:**
  - [validation_method] <!-- How criteria will be verified -->

Strategy & Planning: Task design and formulation checklist

# Task Design & Formulation Checklist

## πŸ”Ή Clarity & Purpose

- [ ] **Is the task clearly defined?**  
       _What exactly needs to be done? Can it be misunderstood?_
- [ ] **Is the goal or outcome explicit?**  
       _What does β€œdone” look like?_
- [ ] **Why is this task important?**  
       _Does it connect to a larger goal or value?_

## πŸ”Ή Scope & Size

- [ ] **Is the task the right size?**  
       _Can it be completed in a single sitting/day/sprint?_
- [ ] **Can it be broken down further?**  
       _Would smaller subtasks improve focus or momentum?_

## πŸ”Ή Context & Dependencies

- [ ] **Are all necessary inputs/resources identified?**  
       _What do I need to start and finish this?_
- [ ] **Are there any dependencies?**  
       _Does this rely on someone/something else first?_

## πŸ”Ή Ownership & Responsibility

- [ ] **Is it clear who owns this task?**  
       _Who is responsible for completing it?_
- [ ] **Is it delegated appropriately?**  
       _Does the person have the skills and context needed?_

## πŸ”Ή Time & Priority

- [ ] **Is there a due date or time estimate?**  
       _When should it be done? How long might it take?_
- [ ] **Is it urgent or important (or both)?**  
       _How does this rank among other tasks?_

## πŸ”Ή Motivation & Friction

- [ ] **Is the task intrinsically motivating or rewarding?**  
       _Is there something engaging about it?_
- [ ] **Are there potential blockers or friction points?**  
       _What might make someone hesitate to start or finish?_

Execution & Management: Dev Task Description

<!--
template_type: dev_task_description
project: [project_name]
status: [planning|in_progress|code_review|testing|completed]
priority: [high|medium|low]
-->

# πŸ› οΈ Dev Task Description: [dev_task_name] <!-- Clear, descriptive name for this dev task -->

- **🏷️ Title:** [task_title] <!-- Short, descriptive title -->
- **🎯 Objective:** [task_objective] <!-- What is the goal of this task? What problem are we solving? -->
- **πŸ“š Context:** [task_context] <!-- Provide background information and the current situation. Explain the environment or previous work that led to this task -->
- **❓ Why This Task:** [task_reasoning] <!-- Explain the reasoning behind the task. Why is it necessary? What benefits or improvements will it bring? -->
- **πŸ’₯ Impact:** [task_impact] <!-- Describe the expected positive outcomes or changes resulting from this task -->
- **πŸ› οΈ Description:** [task_description] <!-- Outline the functionality or changes to be implemented. Include key requirements and any constraints -->
- **πŸ§‘β€πŸŽ¨ Design Considerations:** [design_considerations] <!-- Discuss any technical or design decisions. Explain why certain approaches or solutions were chosen over others -->
- **πŸ€” Other Approaches:** [alternative_approaches] <!-- List alternative solutions considered and explain why they were not selected -->
- **πŸ₯‡ Result:** [success_criteria] <!-- Describe what a successful completion of the task looks like. Define qualitative success criteria -->
- **πŸ’­ Notes:** [additional_notes] <!-- Include any extra insights, references, or considerations relevant to understanding the task -->

Strategy & Planning: Task design and formulation checklist

<!--
template_type: task_design_checklist
project: [project_name]
status: [template|in_use|completed]
priority: [high|medium|low]
-->

# Task Design & Formulation Checklist: [task_checklist_name] <!-- Clear, descriptive name for this task design checklist -->

## πŸ”Ή Clarity & Purpose

- [ ] **Is the task clearly defined?**  
       [task_definition_clarity] <!-- What exactly needs to be done? Can it be misunderstood? -->
- [ ] **Is the goal or outcome explicit?**  
       [goal_outcome_explicit] <!-- What does "done" look like? -->
- [ ] **Why is this task important?**  
       [task_importance] <!-- Does it connect to a larger goal or value? -->

## πŸ”Ή Scope & Size

- [ ] **Is the task the right size?**  
       [task_size_appropriate] <!-- Can it be completed in a single sitting/day/sprint? -->
- [ ] **Can it be broken down further?**  
       [task_breakdown_possible] <!-- Would smaller subtasks improve focus or momentum? -->

## πŸ”Ή Context & Dependencies

- [ ] **Are all necessary inputs/resources identified?**  
       [inputs_resources_identified] <!-- What do I need to start and finish this? -->
- [ ] **Are there any dependencies?**  
       [dependencies_identified] <!-- Does this rely on someone/something else first? -->

## πŸ”Ή Ownership & Responsibility

- [ ] **Is it clear who owns this task?**  
       [ownership_clear] <!-- Who is responsible for completing it? -->
- [ ] **Is it delegated appropriately?**  
       [delegation_appropriate] <!-- Does the person have the skills and context needed? -->

## πŸ”Ή Time & Priority

- [ ] **Is there a due date or time estimate?**  
       [timeline_defined] <!-- When should it be done? How long might it take? -->
- [ ] **Is it urgent or important (or both)?**  
       [priority_clear] <!-- How does this rank among other tasks? -->

## πŸ”Ή Motivation & Friction

- [ ] **Is the task intrinsically motivating or rewarding?**  
       [task_motivating] <!-- Is there something engaging about it? -->
- [ ] **Are there potential blockers or friction points?**  
       [friction_points_identified] <!-- What might make someone hesitate to start or finish? -->