Amanoba Logo
Back to Course

Maintenance and iteration plan

Day 30 of 30 · Generative AI 2026: Build AI Apps and Agents

One-liner: Plan the next 30 days of improvements after launch.
Time: 20 to 30 min
Deliverable: Iteration Roadmap

Learning goal

You will be able to: Create a 30 day iteration plan based on real signals.

Success criteria (observable)

  • The plan lists 3 priorities with reasons.
  • Each priority has a clear owner or next action.
  • A review cadence is scheduled.

Output you will produce

  • Deliverable: Iteration Roadmap
  • Format: Roadmap list
  • Where saved: Course folder under /generative-ai-2026-build-ai-apps-and-agents/

Who

Primary persona: Digital nomad planning the next iteration cycle Secondary persona(s): Users who expect ongoing improvements Stakeholders (optional): Collaborators

What

What it is

A short plan for what you will improve in the next 30 days. It is based on feedback, usage, and business goals.

What it is not

It is not a long term product roadmap or a feature wishlist. It is a focused short term plan.

2-minute theory

  • Short iteration cycles keep you close to user needs.
  • Clear priorities prevent random work.
  • Regular reviews keep the plan relevant.

Key terms

  • Iteration roadmap: A short list of improvements for a set period.
  • Review cadence: A scheduled check to update priorities.

Where

Applies in

  • Product planning
  • Team updates

Does not apply in

  • Marketing campaigns only

Touchpoints

  • Roadmap doc
  • Weekly check in
  • Feedback notes

When

Use it when

  • You have launched the MVP
  • You want to decide what to improve next

Frequency

Every 30 days

Late signals

  • No clear priorities
  • Repeated user issues not addressed

Why it matters

Practical benefits

  • Clear focus for improvements
  • Better alignment with user needs
  • Measurable progress

Risks of ignoring

  • Random changes without impact
  • Users feel ignored

Expectations

  • Improves: focus and learning
  • Does not guarantee: growth

How

Step-by-step method

  1. Review feedback and usage data.
  2. Pick the top 3 priorities.
  3. Define owners or next actions.
  4. Schedule a review date.

Do and don't

Do

  • Base priorities on real signals
  • Keep the list short

Don't

  • Add too many items
  • Plan without data

Common mistakes and fixes

  • Mistake: Too many priorities. Fix: Reduce to three.
  • Mistake: No review date. Fix: Schedule one.

Done when

  • Three priorities are listed.
  • Owners or actions are defined.
  • Review date is scheduled.

Guided exercise (10 to 15 min)

Inputs

  • Feedback list
  • Usage metrics

Steps

  1. List top issues and opportunities.
  2. Choose three priorities.
  3. Assign owners or next actions.

Output format

Field Value
Priority
Reason
Owner or next action
Review date

Pro tip: If a priority does not change the user outcome, drop it.

Independent exercise (5 to 10 min)

Task

Remove one priority and explain why it is lower value.

Output

Revised roadmap.

Self-check (yes/no)

  • Are priorities tied to signals?
  • Are owners or actions defined?
  • Is the review date scheduled?
  • Is the list short?

Baseline metric (recommended)

  • Score: 3 priorities defined
  • Date: 2026-02-06
  • Tool used: Notes app

Bibliography (sources used)

  1. Continuous Discovery Habits. Teresa Torres. 2024-01-01. Read: https://www.producttalk.org/continuous-discovery-habits/

  2. Lean Startup. Eric Ries. 2024-01-01. Read: https://theleanstartup.com/

Read more (optional)

  1. Product Roadmap Basics Why: Simple planning for small teams. Read: https://www.atlassian.com/agile/product-management/product-roadmaps