Alberta Variety Selection Tool
Agenda
Our process for developing digital solutions
How we'll apply this approach to the Alberta Variety Selection Tool
Seed World Group
Process Overview
We follow a structured approach to move from initial concept to a build-ready plan.
Here's how it works.
How the Blueprint turns planning into decisions
The planning phase is designed to answer the questions that matter before development begins.
1
Solution recommendation
The recommended format for Phase 1, such as a website tool, web app, or mobile app.
2
Scope & features
What belongs in the first release and what should be phased later.
3
Rollout strategy
A phased roadmap that protects the first release while leaving room to grow.
4
Budget & timeline
Guidance on likely cost range, timing, and the practical sequence of work.

Outcome: a comprehensive, standalone planning package that defines scope, priorities, budget guidance, timeline guidance, and the recommended path forward — ready to share with any development partner.
What's included in the Product Blueprint
A structured planning document that defines the recommended direction for the first release and the path forward.
Core sections
  • Executive summary and business objectives
  • Audience overview and use cases
  • Recommended solution direction
  • Phase 1 scope and feature structure
  • Must-have vs nice-to-have priorities
  • Rollout strategy and roadmap
  • Budget guidance, timeline guidance, and build recommendation
Key decisions it helps answer
  • What should the first release include?
  • What belongs later?
  • What format fits best for Phase 1?
  • How should features be prioritized?
  • What is the likely scope, budget, and timeline?
Alberta Variety Selection Tool
Solution Exploration
Explore the three possible solution paths (website tool, web app, mobile app)
Key Considerations & Recommendations
Review key considerations and recommendations for the Alberta Variety Tool
Next Steps
Define next steps to move forward
Three possible solution paths
Each option can work — the right choice depends on the user experience needed for the first release and the longer-term vision.
1
Website tool
  • Lives on a website
  • Strong for simple browsing or filtering support
  • Fastest to launch
  • Best when the first release is straightforward and informational
2
Web app
  • Interactive browser-based product
  • Works well on desktop and mobile
  • Supports richer functionality and future growth
  • Often the strongest balance for a decision-support experience
3
Mobile app
  • Downloaded from an app store
  • Best when phone-specific functionality is critical
  • Highest cost and maintenance overhead
  • Usually best only when there is a clear reason to require it

The purpose of the Product Blueprint is to confirm the right format for Phase 1 before development begins.
A practical next step
A simple path from today's discussion to implementation readiness.
1
Today's discussion
Align on the concept, goals, and direction.
2
Discovery session
Gather requirements, priorities, and assumptions in a structured working session.
3
Product Blueprint delivery
Document the solution direction, scope, rollout strategy, budget guidance, and timeline guidance.
4
Build planning
Use the Blueprint to move into design and development with clarity.

The goal is to define the right first release before development decisions are made.