We understand that everyone begins their product journey from a different place, with different needs. Each customer has unique, skills, backgrounds, talents. Line therefore develops a custom tailored product road mapping plan for each project.
Some clients come to the table with a great idea. A spark. A thing that has never been done before. An idea for a new business. Something that requires care and cultivation. For projects like these, our product road mapping phase starts from the very beginning. Through a series of User-Centered design exercises including “practice pitching”, developing a domain-specific vernacular, drawing user flows, and building prototypes, Line joins your team to take help put the definition around your idea so that you are ready to move forward with clarity and confidence.
Some customers have a crystal clear understanding of their product vision and digital strategy. These customers require basic product validation and assistance to extract their goals and convert them to an actionable development plan.
what happens during discovery?
We will assemble a customized schedule for each client depending on their objectives and scale of the product. Here are examples of the types of activities that take place during Line’s Product Road Mapping phase:
Stakeholder interviews (Stakeholders, employees, end-users)
Identify product “critical path”
Visual design concepts
Product backlog building (features/function matrix)
Create taxonomy of themes, epics, and user stories
Create product backlog
Identify organizational gaps
Formulate a high level project plan
Generate a domain-specific vernacular
Draw user flows
Conduct architecture and technology deep-dive
What you walk away with
Each Line Discovery phase culminates in the delivery of the Line Product Road Map which contains:
Executive Summary (concise statement expressing current state, target state, and what will occur to achieve the target)
Visual representation of product landscape
3-4 Product concepts
Systems Architecture Diagrams (Current and target)
Themes and Epics, estimated as relative complexity
Risk assessment of epics
Recommended design and development team structure
Glossary of domain-specific terminology
Design and development schedule
- Development estimates