Process & Strategy

To get the right answer, you have to ask the right questions. Incomplete or incorrectly assumed inputs will result in compromised outcomes. Every project needs a solid foundation which accurately captures the needs of stakeholders and users and clearly articulates requirements. Discovery (fact-finding) is a critcal first step.

At a high level, the process is similar but the individual tactics may changeb based on the project. The more complicated the deliverable, the more important it is to follow a process and ensure nothing is overlooked. I can help you define the problem and achieve an effective solution.

Process


The process always starts with some form of discovery, or requirements gathering from audience and stakeholder interviews that include perspectives at all levels in the org. It then proceeds through the '5 Ds'. Discovery is codified in the definition, which sets the framework for everything to follow.
Process Diagram Overview

Design-develop-deploy are distinctly different steps performed by different teams... however they are incredibly interdependent and must be driven by shared vision and scope. It's important that each team member has input and feedback at key stages in the project. This can be a waterfal or agile process, or something in between.
Process Waterfall/Agile Breakdown

The individual exercises used vary with the scope of the project and the type of deliverable—it's not one size fits all. Each exercise is a tool to expose stakeholder or user perspective and reveal scope and functionality that will impact the final deliverable.

Examples of Exercises

  • Stakeholder Interviews
  • KJ Sessions
  • Defining Success
  • Documenting Scope
  • Collaborative Sketching
  • Focus Groups
  • Audits (Content, Data, Technical)
  • User Journeys
  • Site or Product Map
  • Wireframes
  • Rapid Prototyping
  • User Testing
Example of a KJ (Sticky) Session Flow of Data Between Properties and Databases Whiteboard Sketching Collaborative Wireframe Sketching