1. Discovery

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

  • Practice pitching

  • 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)

  • Product Backlog

  • 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

2. Design

Once we have a roadmap, we figure out how to break up our work into several iterations. During a design period, we look at a single iteration, and conduct as much upfront systems, software, and experience design as needed to get us to development as quickly as possible.



For startup-scale projects, the design phase typically lasts 1-3 weeks depending on scope and complexity. The aim is to offer minimal upfront planning to produce a skeletal planning document with the understanding that detail will be provided throughout an ongoing iterative development process.


Enterprise scale projects require greater upfront planning. That’s because:

  • There’s more dependence on and coordination required with external teams

  • Extra time is required to plan and collaborate with third-party vendors

  • The application likely has a greater number of integration points

  • There are likely greater requirements for performance at scale

  • There is an increased consideration for privacy and data security

Therefore, Line will require more upfront time to perform a detailed design. We author comprehensive technical documentation and annotated wireframes for the entire application during this phase which can last 1-3 months depending on project scope and complexity.


What happens during the design period?

    Depending on detail required, during the design phase, the team will:

    • plan and document project implementation details

    • work with the client, third-party vendors, and others to understand business logic and document business requirements

    • produce functional wireframes

    • produce core visual assets (logo, look-and-feel, project templates)

    • identify and document known integration points

    • define and document system-wide entities, entity relations, entities' data fields, and entity states

    • Define system and software architecture

    • Define deployment architecture

    • identify technically complex/risky areas of the software application

    • identify third party libraries and tools that can be leveraged to accelerate development

    • highlight any known risk areas

    • assemble a quality assurance plan

    • create a detailed development schedule

    • identify target devices and browsers

    • create a Privacy and Security plan

    • make a deployment and release management plan

    • produce a Client Empowerment Plan

    What You'll Walk Away with

    • Technincal Document
    • Detailed Wireframes
    • Test Plan
    • Core visual assets