This page is intended to function as copy-paste-helper for note-taking, brainstorming, refreshing memory or simply for inspiration.
# ποΈ 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]
# π― OKR
- **π― Objective:**
- [What is to be achieved?]
- **π Key Results:**
- [ ] KR1: [Measurable outcome]
- [ ] KR2: [Measurable outcome]
- **π Review Date:**
- [YYYY-MM-DD]
# π£οΈ Roadmap
- **π Timeframe:**
- [Start Date] to [End Date]
- **π Key Initiatives:**
- **Initiative 1:**
- [Description, timeline]
- **Initiative 2:**
- [Description, timeline]
- **ποΈ Milestones:**
- [List of major milestones]
# π― 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]
# π 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]
# ποΈ Governance Model
- **π§ Decision-Making Structure:**
- [Who makes decisions]
- **π£οΈ Policies:**
- [Key guiding policies]
- **π΅οΈββοΈ Roles & Responsibilities:**
- [List governance roles]
- **π² Review Cycle:**
- [Frequency of review]
# π₯ Stakeholder Map
| Stakeholder | Role | Interest/Influence | Allocation (%) |
| ------------ | ------ | ------------------ | -------------- |
| [Name/Group] | [Role] | [High/Medium/Low] | [Percentage] |
# πΊοΈ 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".]
# 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?
# Pitch
For **target audience** who need **opportunity/pain**, **product/service** provides **solution**. Unlike **alternatives** it **differentiators**.
# π 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]
# π 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?]
# π― 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]
# π― 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
# π 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:**
- 
- **π₯οΈ 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]
# π€ 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]
# π 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**.
# π· 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]
# π€οΈ 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]
# π€ Persona
- **π Name:** [Name]
- Example: Jane Doe
- **πΌ Role:** [Role]
- Example: Maintenance Technician
- **πΌοΈ Picture:**
- [Photo or illustration]
- **π― Focus:**
- [Key interaction aspect]
- **π Notes:**
- [Motivations, goals, challenges]
# π 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]
# π 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]
# π 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 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.]
# π 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?**
# π 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]
# π 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]
# π¨ 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]
# πΌοΈ 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.
# π’ 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]
# π
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]
# ποΈ 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]
# π 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]
# π 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]
# βοΈ 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]
# π 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]
# π 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]
# ποΈ 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] |
# π 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]
# π‘ Lessons Learned
- **π Project/Incident:**
- [Name]
- **π What Worked:**
- [Successes]
- **π What Didnβt Work:**
- [Challenges]
- **π‘ Recommendations:**
- [Future improvements]
# π 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]
# β‘ 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]
# π 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]
# π Feature Brief
- **π Summary:**
- [Brief overview of the feature]
- **π― Purpose:**
- [Why this feature is needed]
- **π₯ Impact:**
- [Expected benefits]
- **π Key Components:**
- [Component 1]
- [Component 2]
# π Acceptance Criteria
- **π Feature/Task:**
- [Name]
- **π Criteria:**
- [ ] Criterion 1: [Description]
- [ ] Criterion 2: [Description]
- **π Validation:**
- [How criteria will be verified]
# π οΈ 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.]