Smart-Recovery Execution Readiness Kit - Week 2

Turn Week 1 discovery into a credible Phase 1 product approach, delivery backlog, wireframe, and executive approval case.

What this week covers

This standalone coursework project helps you complete Week 2 of the course:

• define a focused Phase 1 scope
• assess change risk using ADKAR
• create a prioritised Jira-style backlog
• prototype the Smart-Recovery portal flow
• prepare an executive briefing using The Pyramid Principle

Getting setup

1. Download or copy this folder into your working area.
2. Open the folder in your editor.
3. Bring your Week 1 outputs with you or use the starter assumptions in this project.
4. Read docs/README.md first for the recommended sequence.
5. Use the templates in templates/ before creating polished versions in submissions/.

Tech requirements

This is a documentation and artefact project.

Recommended tools:

• Jira or a spreadsheet equivalent
• Figma or any wireframing tool
• PowerPoint, Google Slides, or Markdown
• Excel or Google Sheets for story and traceability tables

How to use this project

1. Define your Phase 1 scope in docs/01-phase-1-scope-template.md.
2. Complete the ADKAR and backlog templates in templates/.
3. Use docs/03-wireframe-annotation-guide.md while building your Figma flow.
4. Draft the executive narrative using docs/04-executive-briefing-storyboard.md.
5. Save final outputs in submissions/.

Success looks like

You are on track if you can produce:

• a clear in-scope and out-of-scope Phase 1 statement
• an ADKAR analysis that affects what goes into the backlog
• at least 15 technical user stories with acceptance criteria and dependencies
• a low-fidelity wireframe with main and exception paths
• an executive recommendation that starts with the answer, not the history

Files explained

• docs/ - guidance for scope, backlog quality, wireframes, and executive messaging
• templates/ - working CSVs and markdown structures for backlog, ADKAR, and storyboard preparation
• data/ - reference inputs to help trace Week 1 value into Week 2 delivery choices
• submissions/ - where you place your final Phase 1 outputs

Troubleshooting

My scope is getting too big

Re-read your Week 1 top opportunities and ask which items are essential for a believable first release.

My backlog feels like a list of screens

Add routing, reporting, audit, and agent visibility stories. They are part of the operating model, not optional extras.

My wireframe looks polished but thin

Reduce visual polish and add more annotations, rules, and exception paths.

My executive deck sounds like a project diary

Rewrite slide 1 as a decision statement. Then group the rest of the deck under three supporting arguments.

Tests

There is no automated test runner. Use the checklists in docs/ and submissions/README.md to self-review.