Technical Discovery Canvas

A process for de-risking investment in technology

A Technical Discovery is a process that can de-risk investment in technology. We create value for customers by solving their problems. If we create products to serve user needs, then people will use and value them. Alongside understanding the needs of the customer, we need to uncover how technology can meet and underpin those needs.

I've created a Technical Discovery Canvas — ten basic building blocks in a pre-structured canvas that helps teams draw out, discuss, and discover technology choices with user needs and desired business outcomes at their core.

1. Problem definition

Reframe the project as a problem to be solved. Build a shared understanding of the problem. Break down your assumptions and ask lots of questions. Reframing the problem also includes agreeing what is and isn't part of the project.

As a team, ask yourselves: Why are we doing this? What do we do now and why? What critical things are we assuming? How will we know if we're successful? Who are our stakeholders?

2. Business outcomes and measurement

How will you prove that you've been successful? Think about what data you'll collect to measure performance and what performance metrics you'll use. Ask your stakeholders what success looks like for them. Measure what's happening now so you begin to understand how much the problem is currently costing.

3. User needs

Without good knowledge of user needs, we are building on a bed of sand. By understanding what types of users and customers we should focus on, we ensure we are focused on creating experiences they will value.

4. User outcomes and benefits

As a team, ask what the user is trying to accomplish. How will they think and feel during and after this process? What behaviours will they change as a result?

5. Activities

What are the activities that the user will do to complete their goal? Map out those activities. This may help identify opportunities for improvement and highlight where user pain points are.

6. Capabilities, resources and data

What capabilities, resources and data do we need to provide to support the user to carry out those activities?

7. Technology

Without solutionising, think about what types of technology, systems and tools are required to support those user activities. This helps compile a shopping list of tech that supports the user journey.

8. Selection criteria

Define some criteria from the user needs and business requirements that will help you evaluate the technology. Examples: affordability, maintainability, interoperability, scalability.

9. Exploration and assessment

With your shopping list of technology types, start exploring potential services and tools. Create a matrix and score each option against each of your criteria.

10. Candidate solution

Create a candidate solution — a technical architecture — from your highest scoring technologies. This will form a hypothesis: we believe we will achieve this business outcome, if these users attain this benefit, with this solution.

With your candidate solution you can conduct experiments to validate its viability. Always think about the least amount of work you need to do to learn the next most important thing.

Read more