This page is intended to function as copy-paste-helper for note-taking, brainstorming, refreshing memory or simply for inspiration.
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
# π₯ Stakeholder Map
| Stakeholder | Role | Interest/Influence | Allocation (%) |
| ------------ | ------ | ------------------ | -------------- |
| [Name/Group] | [Role] | [High/Medium/Low] | [Percentage] |
<!--
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" -->
<!--
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 -->
<!--
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 -->.
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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
<!--
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:**
-  <!-- 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 -->
<!--
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 -->
<!--
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].
<!--
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 -->
<!--
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" -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 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.]
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
# π 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]
# βοΈ 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]
<!--
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 -->
<!--
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 -->
<!--
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] |
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
<!--
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 -->
# 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?_
<!--
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 -->
<!--
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? -->