<aside> 💡 Spikes and proof-of-concept (PoC)documents are invaluable to not lose track of past research, its learnings and potential next steps. When building new features, it’s very important to understand what you are getting in, to avoid as many surprises as you can. This template is one that helped me as manager to assess risk and prioritise work.

</aside>

Outline properties:

Product Direction:

Link to documents outlining where the whole project should be going. This is important to provide context.

Days of initial investment: **

How much time can you spend on this research

Goal of this discovery:

Describe the target of this discovery as detailed as possible.

DRI:

Who is the direct responsible individual

Discovery:

<aside> 💡 Keep notes of all your findings and resources. Be as detailed as you can as very often these documents might end up being evaluated and sit around for a few weeks before next steps are taken. Maybe even someone else will implement or work on this, so all context is important. Following you’ll find some good points that should be addressed as part of the discovery.

</aside>

Questions to answer:

• How are we building this?
• Technical feasibility — do we likely need to redo a lot the implementation for next steps in the future?
• Whats the fastest way to reach our goal?
• What’s the biggest risk with this implementation?
• How much time will this take?
• How are we testing this feature and avoid accidental breakage?