🔍 Initial Expectations

✅ What this stage is about

Every idea starts with hope — that it’ll help someone, solve something, or lead somewhere exciting.

This step helps you capture those early expectations clearly and positively. You’ll map what success might look like, what you'd love to see happen, and what you expect could be tricky.

✨ Think of this as a “note to your future self” — setting a vision, not writing a contract.

🎯 What you’ll learn

How to describe your early goals and assumptions
How to shape “what good looks like” — for users and for you
How to spot potential challenges before they surprise you
How to start measuring what matters

🛠️ Tools and methods

✅ Expectation mapping grid — 3-part reflection (BG4 color-coded)
🟢 What we hope happens
🔵 What we’re unsure about
🟣 What might be hard
Goal prompts like “We’ll know it’s working if...”
Simple success metrics (usage, feedback, signals of progress)

⚠️ Common gaps

Jumping in without a shared vision
Avoiding hard questions (e.g. pricing, feasibility)
Assuming smooth sailing
Confusing expectations with outcomes

🧠 Tips from the field

“Be ambitious and honest. It's okay to dream, but better to write it down and refine later.”
— Product lead, IEN contributor

“Early expectations aren’t about being right — they’re about setting direction.”

📚 Helpful links & resources

Viability Sprint →
Customer Jobs →
QFD Analysis →
🔗 Download: Initial Expectations Worksheet (DOCX)

📄 Worksheet_0103_Initial_Expectation.docx

✍️ Quick prompts — Fill in your first expectations

✅ What would success feel like to your user?
🎯 What would success look like to your team?
🚀 What’s the first sign you’re onto something?
🤔 What worries or blockers do you already see?
📏 How might you measure “progress” in 30 days?

💡 These are starting points, not commitments — treat them like working notes.