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

# πŸ”οΈ Milestone: Demoable version

-   **πŸ“† Target Date:**
    -   [YYYY-MM-DD] End of February
-   **πŸ“† Completion Date:**
    -   [YYYY-MM-DD]
-   **🎯 Objective:**
    -   First prototyped version of the design demoed for stakeholders
-   **πŸ“  Key Results:**
    -   [ ] KR1: First idea of the design is documented with key points highlighted.
    -   [ ] KR2: Identify and confirm UI component needs.
    -   [ ] KR3: Gather remarks and feedback from stakeholders and assess next steps.
-   **πŸͺ€ Tripwires:**
    -   Lack of access to the user study documents β†’ Postpone stakeholder demo/review
-   **πŸ‘€ Reviews:**
    -   **[Review date]:**
        -   **What went well:**
            -   [Add key wins]
        -   **Challenges faced:**
            -   [Add key obstacles]
        -   **Action plan for improvements:**
            -   [Next steps]

Strategy & Planning: OKR

# 🎯 OKR

-   **🎯 Objective:**
    -   [What is to be achieved?]
-   **πŸ“  Key Results:**
    -   [ ] KR1: [Measurable outcome]
    -   [ ] KR2: [Measurable outcome]
-   **πŸ“† Review Date:**
    -   [YYYY-MM-DD]

Strategy & Planning: Roadmap

# πŸ›£οΈ Roadmap

-   **πŸ“† Timeframe:**
    -   [Start Date] to [End Date]
-   **πŸ”‘ Key Initiatives:**
    -   **Initiative 1:**
        -   [Description, timeline]
    -   **Initiative 2:**
        -   [Description, timeline]
-   **πŸ”οΈ Milestones:**
    -   [List of major milestones]

Strategy & Planning: Business Goal

# 🎯 Business Goal

-   **πŸ“Œ Business Goal Name:**
    -   [Name] (e.g. Minimize Equipment Downtime)
-   **🎯 Objective Statement:**
    -   [Clear, measurable outcome]
-   **πŸ“Š Supporting Metrics:**
    -   [KPIs, e.g., MTTR, MTBF]
-   **πŸ” Strategic Importance:**
    -   [Why it matters for the business]
-   **πŸ”— Dependencies:**
    -   [Related factors or systems]

Strategy & Planning: Business Process

# πŸ”„ Business Process

-   **πŸ“Œ Process Name:**
    -   [Name]
-   **πŸ“ Stages:**
    -   [List key steps]
-   **😞 Pain Points:**
    -   [List challenges]
-   **πŸš€ Opportunities:**
    -   [Areas for improvement]
-   **πŸ”„ Inputs / Triggers:**
    -   [What starts the process]
-   **βœ… Outputs / Results:**
    -   [Expected outcomes]
-   **πŸ‘₯ Key Stakeholders:**
    -   [Roles involved]

Strategy & Planning: Governance Model

# πŸ›οΈ Governance Model

-   **🧠 Decision-Making Structure:**
    -   [Who makes decisions]
-   **πŸ—£οΈ Policies:**
    -   [Key guiding policies]
-   **πŸ•΅οΈβ€β™‚οΈ Roles & Responsibilities:**
    -   [List governance roles]
-   **🚲 Review Cycle:**
    -   [Frequency of review]

Strategy & Planning: Stakeholder Map

# πŸ‘₯ Stakeholder Map

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

Strategy & Planning: Strategy

# πŸ—ΊοΈ Strategy

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

Strategy & Planning: Key questions before starting the work

# Key questions before starting the work

-   **πŸ’Ž What is worth it?**
    -   What are we certain we can actually achieve, both in terms of tasks and outcomes, given the constraints of reality?
    -   From organisation's point of view: will all items return the investment?
    -   From our point of view: will all items be worth of our time, budget and resources?
    -   From users' point of view: will all items bring real value to users?
    -   Are we able to provide support and maintenance, and improve the work after the work is done?
-   **πŸ–ΌοΈ What are we doing?**
    -   Is the goal understandable to all involved?
    -   Is the current plan and content accessible to all involved?
    -   Is the timeline and milestones clear to all involved?
-   **πŸ’Ά What is the value of the outcome?**
    -   Who are we creating value for? Who is the target audience?
    -   What is the underlying critical need that we aim to address?
    -   How is the outcome going to differentiate from alternatives? Who or what are the direct and indirect competitors?

Strategy & Planning: Pitch

# Pitch

For **target audience** who need **opportunity/pain**, **product/service** provides **solution**. Unlike **alternatives** it **differentiators**.

Research: Contextual inquiry

# πŸ” Contextual inquiry

## 1. Session Information

-   **πŸ—“οΈ Date & Time:** [YYYY-MM-DD HH:MM]
-   **πŸ“ Location/Setting:** [Location description]
-   **🎯 Objective:** [Main focus of this inquiry session]
-   **🎯 Context:** [Main context, e.g. related project or design track]

## 2. Participant Details

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

## 3. Environment & Setup

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

## 4. Observed Tasks & Behaviors

-   **πŸ“ Tasks Overview:**
    -   [List and describe the key tasks the participant is performing]
-   **⏱️ Task Duration & Sequence:**
    -   [Time taken per task or the order in which tasks are performed]
-   **πŸ” Behaviors & Interactions:**
    -   [Detailed observations of how the participant interacts with the system]

## 5. User Feedback & Quotes

-   **πŸ’¬ Direct Quotes:**
    -   [Record verbatim quotes that provide insight]
-   **πŸ™‚ Positive Feedback:**
    -   [What aspects of the experience did the participant like?]
-   **😟 Pain Points/Frustrations:**
    -   [List any issues, confusion, or challenges observed]

## 6. Insights & Opportunities

-   **πŸ’‘ Key Insights:**
    -   [Summarize the main takeaways from the session]
-   **πŸš€ Opportunities for Improvement:**
    -   [Identify potential improvements or new ideas based on observations]

## 7. Follow-Up Actions

-   **πŸ”„ Next Steps:**
    -   [Outline any planned follow-up interviews, tests, or design adjustments]
-   **πŸ“Œ Additional Notes:**
    -   [Any extra observations or context that might be useful later]

Design & Problem Solving: Develop shared vision with triads

# πŸ“ Develop shared vision with triads

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

-   **🧠 Step 1: Describe the product/service**
    -   [Brainstorm words (10+) that describes the product or service]
-   **πŸ“ Step 2: Pick words in group of three**
    -   [Pick three words that put together desribes the product]
-   **πŸ—£οΈ Step 3: For each group: Describe**
    -   [Related nouns (5-10): what nouns do you think of when you see the words? (system objects)]
    -   [Related verbs (5-10): what verbs do you think of when you see the words? (system actions)]
    -   [Related adjectives (5-10): 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**
    -   [What kind of experience do you envision?]
    -   [What would be the most important parts of the product/service?]
    -   [How would the product/service work?]
    -   [How would users and customers feel about it?]

Design & Problem Solving: JTBD

# 🎯 Job to Be Done (JTBD)

-   **πŸ§β€β™‚οΈPerson:**
    -   [Who is trying to accomplish this?]
-   **πŸ‘· Job Statement:**
    -   [When I... I want to... so I can...]
-   **😣 Pain Points & Frictions:**
    -   [ ] [Issue 1]
    -   [ ] [Issue 2]
-   **πŸ† Success Criteria:**
    -   [What success looks like]
-   **πŸ”Ή Existing Alternatives / Workarounds:**
    -   [Current workaround or alternative solution]
-   **πŸ—οΈ Proposed Solution (if applicable):**
    -   [Brief description]
-   **❓ Open Questions / Risks:**
    -   [Uncertainties or blockers]

Design & Problem Solving: JTBD hierarchy

# 🎯 Job to Be Done (JTBD) hierarchy

-   **⬇️ Why:**
-   **⬇️ Why:**
-   **⬇️ Why:**
-   **⬇️ Why:**
-   **Job Statement:** [When I... I want to... so I can...]
-   **⬆️ How:**
-   **⬆️ How:**
-   **⬆️ How:**
-   **⬆️ How:**

## 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

# πŸ› UX Issue [Name]

-   **πŸ“Œ Summary:**
    -   [Short, clear description]
-   **πŸ”„ Description:**
    -   [Steps to reproduce, details]
-   **⚠️ Expected vs. Actual:**
    -   😊 _Expected:_ [What should happen]
    -   ❌ _Actual:_ [What actually happens]
-   **🎨 UI Elements Affected:**
    -   [List components/screens]
-   **πŸ“· Screenshots / Recordings:**
    -   ![Title](filename.png)
-   **πŸ–₯️ Environment Details:**
    -   Device: [Desktop/Mobile]
    -   OS: [Windows/macOS/Linux]
    -   Browser: [Chrome/Firefox/Safari/Other]
-   **πŸš€ Possible Solutions:**
    -   [Suggestions]
-   **πŸͺ€ Severity & Impact:**
    -   [Critical/Major/Minor/Trivial]
-   **πŸ› οΈ Reported by:**
    -   [email]
-   **πŸ—“οΈ Date Reported:**
    -   [YYYY-MM-DD]

Design & Problem Solving: HMW (How Might We)

# πŸ€” How Might We (HMW)

-   **🎯 Challenge Area:**
    -   [Broad problem space]
-   **πŸ“ Observation / Insight:**
    -   [What have we learned]
-   **πŸ’‘ How Might We:**
    -   HMW [action] for [user] so that [desired outcome]?
-   **πŸ› οΈ Constraints / Considerations:**
    -   [Limitations]
-   **πŸ”Ή Related:**
    -   [Links or references]

Design & Problem Solving: Problem Statement

# πŸ›‘ Problem Statement

-   **🌍 Context:**
    -   [Background of the issue]
-   **πŸ€• Problem:**
    -   [What is the issue and why it matters]
-   **πŸ‘€ Who is affected:**
    -   [User group or stakeholders]
-   **🎯 Goal / Desired Outcome:**
    -   [What should be achieved]
-   **⚠️ Pain Points / Challenges:**
    -   [Issue 1]
    -   [Issue 2]
-   **πŸ” Supporting Data / Insights:**
    -   [Research, analytics, evidence]
-   **πŸš€ Potential Solutions (if applicable):**
    -   [Suggested approaches]

Our **who/customer segment** are **what/problem** because they **why/reason**.  
If we solve this, it would impact **who/customer segment** positively by **customer benefit** and benefit our business by **business benefit**.

Design & Problem Solving: Double Diamond

# πŸ”· Double Diamond

-   **πŸ“… Date:**
    -   [YYYY-MM-DD]
-   **πŸ‘₯ Participants:**
    -   [List names/emails]

## 1️⃣ Discover

-   πŸ” **Problem Exploration:**
    -   [Understanding the challenge]
-   πŸ—£οΈ **User Research:**
    -   [Key insights]
-   πŸ“Š **Data Analysis:**
    -   [Findings]
-   ❓ **Challenges Identified:**
    -   [Challenge 1]
    -   [Challenge 2]

## 2️⃣ Define

-   🎯 **Key Problem Statement:**
    -   [Clear articulation]
-   😣 **Pain Points:**
    -   [Pain Point 1]
    -   [Pain Point 2]
-   πŸ–ΌοΈ **Scope & Constraints:**
    -   [In/out of scope]

## 3️⃣ Develop

-   πŸ’‘ **Brainstorming Ideas:**
    -   [Idea 1]
    -   [Idea 2]
-   🎨 **Wireframes / Mockups:**
    -   [Links or screenshots]
-   βš™οΈ **Prototype Testing:**
    -   [User feedback]

## 4️⃣ Deliver

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

Design & Problem Solving: User Journey

# πŸ›€οΈ User Journey

-   **πŸ“Œ Name:**
    -   [Journey Name] (e.g. Resolving Equipment Downtime)
-   **πŸ“ Stages:**
    -   [Detection β†’ Reporting β†’ Diagnostics β†’ Repair β†’ Validation]
-   **🎯 User Goals:**
    -   [e.g., Minimize downtime]
-   **😞 Pain Points:**
    -   [e.g., Delayed part delivery]
-   **πŸš€ Opportunities:**
    -   [e.g., Real-time data aggregation]
-   **πŸ”„ Randomness / Variability:**
    -   [e.g., Inconsistent IoT sensor data]
-   **πŸ“‚ Mapped Business Process:**
    -   [e.g., Equipment Maintenance Process]
-   **πŸ“Š Key Metrics:**
    -   [e.g., Reduce Mean Time to Repair]

Design & Problem Solving: Persona

# πŸ‘€ Persona

-   **πŸ“› Name:** [Name]
    -   Example: Jane Doe
-   **πŸ’Ό Role:** [Role]
    -   Example: Maintenance Technician
-   **πŸ–ΌοΈ Picture:**
    -   [Photo or illustration]
-   **🎯 Focus:**
    -   [Key interaction aspect]
-   **πŸ“ Notes:**
    -   [Motivations, goals, challenges]

Design & Problem Solving: Contextual Use Scenario

# 🎭 Contextual Use Scenario

-   **πŸ†” ID:**
    -   [Unique ID, e.g., #001]
-   **πŸ“‚ Group:**
    -   [Scenario group, e.g., Diagnostics]
-   **πŸ‘€ Persona:**
    -   [Example: John Smith]
-   **πŸ“– Description:**
    -   [Narrative explanation]
-   **🎯 User Goal:**
    -   [What the user is trying to achieve]
-   **πŸ’‘ Design Hypothesis:**
    -   [Early design ideas]

Design & Problem Solving: User Story

# πŸ“ User Story

-   **πŸ‘€ Role:**
    -   [User or stakeholder] (E.g. "Maintenance Technician")
-   **🎯 Action / Need:**
    -   [What the user wants to do]
-   **πŸ” Purpose / Benefit:**
    -   [Why it’s needed]
-   **πŸ“Œ Full User Story:**
    -   "As a [role], I want to [action] so that [benefit]."
-   **πŸ”— Dependencies:**
    -   [Tools or conditions required]
-   **πŸ† Outcome:**
    -   [Success criteria]

Design & Problem Solving: Use Case

# πŸ“‘ Use Case

-   **πŸ“Œ Use Case Name:** [Name]
    -   Example: Retrieve Diagnostic Error Codes
-   **🎯 Objective:**
    -   [Purpose of the interaction]
-   **πŸ“ Preconditions:**
    -   [What must be true]
-   **πŸ”„ Steps:**
    1. [Step 1]
    2. [Step 2]
-   **πŸ† Outcome:**
    -   [Expected result]
-   **😞 Pain Points:**
    -   [Potential challenges]
-   **πŸš€ Opportunities:**
    -   [Improvements]
-   **πŸ”— 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

# πŸŒ‰ SFDIPOT Template

## πŸ—οΈ Structure

-   **What is the application's architecture?**
-   **What technologies are used?**
    -   (e.g., databases, APIs, authentication methods)
-   **Are there dependencies on third-party services?**

## βš™οΈ Function

-   **What are the key functionalities of the application?**
-   **List critical user actions and system processes.**
-   **Are there hidden or less obvious functions?**

## πŸ—„οΈ Data

-   **What types of data does the application handle?**
-   **How is data stored, processed, and transmitted?**
-   **Are there validation checks for inputs?**

## πŸ”— Interfaces

-   **What interfaces does the application have?**
    -   (e.g., UI, API, CLI, third-party integrations)
-   **Are there import/export features?**
-   **Are error messages and logs useful and clear?**

## πŸ’» Platform

-   **What platforms does the application support?**
    -   (e.g., OS, browsers, mobile devices)
-   **Are there platform-specific behaviors or issues?**
-   **What are the system requirements?**

## πŸ” Operations

-   **Who will use and maintain the system?**
-   **Are there security, logging, or monitoring considerations?**
-   **What are the backup and recovery strategies?**

## ⏳ Time

-   **Are there time-dependent functions?**
    -   (e.g., scheduling, time zones, expiration dates)
-   **How does the system handle date/time changes (e.g., leap years, daylight saving)?**
-   **Are there performance considerations under peak loads?**

Design & Problem Solving: UX KPI Discovery

# πŸ” UX KPI Discovery

## 1. 🎯 Define UX Objectives & Goals

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

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

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

## 3. πŸ’‘ Brainstorm Potential Metrics

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

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

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

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

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

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

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

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

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

Creative Thinking: Reverse Brainstorm

# πŸ”„ Reverse Brainstorm

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

Creative Thinking: Metaphoric Thinking

# 🎨 Metaphoric Thinking

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

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

# πŸ–ΌοΈ Note-taking framework C-Q-E/I/D-T

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

Comms and docs: Communication Plan

# πŸ“’ Communication Plan

-   **🎯 Objective:**
    -   [Purpose of the communication plan]
-   **πŸ‘₯ Audience:**
    -   [List stakeholder groups]
-   **πŸ“Ί Channels:**
    -   [email, meetings, Slack, Teams, etc.]
-   **πŸ”‰ Frequency:**
    -   [How often communications occur]
-   **πŸ‘¨β€πŸ’Ό Responsible:**
    -   [email]

Comms and docs: Meeting Memo

# πŸ“… Meeting Memo

-   **πŸ—“οΈ Date/Time:**
    -   [YYYY-MM-DD] [HH:MM]-[HH:MM]
-   **πŸ“ Location / Link:**
    -   [Meeting room or video call link]
-   **πŸ‘₯ Attendees:**
    -   [Person 1]
    -   [Person 2]
-   **🎯 Agenda:**
    1. [Topic 1]
    2. [Topic 2]
-   **πŸ“Œ Key Notes & Discussions:**
    -   πŸ“ [Key point]
    -   ❓ [Question raised]
-   **🏒 Decisions Made:**
    -   [Decision 1]
    -   [Decision 2]
-   **πŸš€ APs:**
    -   [ ] [Name] [Action]
-   **πŸ‘Ÿ Next:**
-   **πŸ“‚ Attachments & References:**
    -   [Link or file attachment]

Comms and docs: Meeting Agenda

# πŸ—’οΈ Meeting Agenda

-   **πŸ—“οΈ Date/Time:**
    -   [YYYY-MM-DD HH:MM]
-   **πŸ“ Location / Link:**
    -   [Meeting room or video call link]
-   **🎯 Agenda:**
    1. [Topic 1]
    2. [Topic 2]
-   **🍝 Expected Outcomes:**
    -   [What is to be achieved]

Comms and docs: Decision Record

# πŸ“œ Decision Record

-   **πŸ†” ID:** [Unique ID]
-   **πŸ“… Date:** [YYYY-MM-DD]
-   **πŸ‘€ Author(s):** [email]
-   **πŸ“Œ Status:** (Draft/Proposed/Accepted/Deprecated)
-   **πŸ—οΈ Context:** [Problem and constraints]
-   **πŸ’‘ Decision:** [Chosen solution and rationale]
-   ## **πŸ”„ Alternatives**
    1. **[Alternative 1]** – [Pros/Cons]
    -   2. **[Alternative 2]** – [Pros/Cons]
-   **⚠️ Consequences:** [Implications of the decision]
-   **πŸš€ Next Steps**
    -   [Follow-up action] [Review date]
    -   [Follow-up action] [Review date]

Comms and docs: Pros and Cons

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

-   **🎯 Topic / Decision:**
    -   [What is being evaluated]
-   **πŸ“… Date:**
    -   [YYYY-MM-DD]
-   **πŸ‘€ 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

# πŸ” Assumption

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

Execution & Management: Track

# πŸš€ Track: [Track Name]

-   **πŸ› οΈ Current Status:**
    -   Not started | In Progress | Completed | Pending | Skipped | Postponed
-   **πŸ“Œ Description:**
    -   [Overview of the track]
-   **🎯 Goals & Objectives:**
    -   [What the track aims to achieve]
-   **πŸ“† Timeline:**
    -   Start: [YYYY-MM-DD]
    -   Estimated Completion: [YYYY-MM-DD]
-   **πŸ“‚ Key Deliverables:**
    -   [ ] **Deliverable 1** – Due: [YYYY-MM-DD]
    -   [ ] **Deliverable 2** – Due: [YYYY-MM-DD]
-   **πŸ”— Dependencies:**
    -   [Dependencies or links]
    -   [Link to RACI]
-   **⚠️ Risks & Challenges:**
    -   [Potential blockers]
-   **πŸ“Š Success Metrics:**
    -   [How success is measured]

Execution & Management: RACI

# πŸ—οΈ RACI: [Project/Initiative Name]

**πŸ“Œ 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)

# πŸ“‹ Work Breakdown Structure (WBS)

-   **🏷️ Project Name:**
    -   [Name]
-   **πŸ“‹ Tasks Breakdown:**
    1. **Phase 1:**
    -   Task 1: [Description]
    -   Task 2: [Description]
    2. **Phase 2:**
    -   Task 1: [Description]
    -   Task 2: [Description]
-   **🏁 Milestones:**
    -   [Key milestones]

Execution & Management: Lessons Learned

# πŸ’‘ Lessons Learned

-   **πŸ“ Project/Incident:**
    -   [Name]
-   **πŸ‘ What Worked:**
    -   [Successes]
-   **πŸ‘Ž What Didn’t Work:**
    -   [Challenges]
-   **πŸ’‘ Recommendations:**
    -   [Future improvements]

Execution & Management: Risk Register

# πŸš€ 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:**
    -   [How risks will be reviewed]

Execution & Management: Change Request

# ⚑ Change Request

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

Execution & Management: Retrospective Summary

# πŸ”„ Retrospective Summary

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

Execution & Management: Feature Brief

# 🌟 Feature Brief

-   **πŸ“ Summary:**
    -   [Brief overview of the feature]
-   **🎯 Purpose:**
    -   [Why this feature is needed]
-   **πŸ’₯ Impact:**
    -   [Expected benefits]
-   **πŸ”‘ Key Components:**
    -   [Component 1]
    -   [Component 2]

Execution & Management: Acceptance Criteria

# πŸ‘Œ Acceptance Criteria

-   **πŸš€ Feature/Task:**
    -   [Name]
-   **πŸ“‹ Criteria:**
    -   [ ] Criterion 1: [Description]
    -   [ ] Criterion 2: [Description]
-   **πŸ‘Œ Validation:**
    -   [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

# πŸ› οΈ Dev Task Description

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