This is the part where you do what you do best – make products and services. Yet defining what is to be built often slows down development teams because there are too many unknowns and no clear path to answering them. Contrary to popular belief, you can schedule the process to take the concept and move it to a design. We’ll show you how.
Specifying the Interfaces
Two types of interfaces – human interfaces and machine interfaces – need to be defined for any product or service. So many times the machine (or internal) interfaces are specified first and then the human interfaces are made to wrap the machine interfaces. Unfortunately, this process is backwards. How your offering works for the customer is the single most important thing you can focus on. Using user-centered design techniques, we’ll help you work through the development and refinement of the human interfaces and then make sure that the solution can be adapted to your internal infrastructure.
Estimating Costs, Timelines, and Profits
The business model is as important (if not more so) as a product design because you need to make money. From the very start, you’ll want a rough estimate of the cost of the project and the final offering. Plus you’ll want to begin to sketch out pricing. If you don’t have a framework for tracking costs, timelines, and margins for your product or service, we’ll help you develop one. Not after it is half way finished, but before the work starts.
Once again, your customer will need to be in the loop. As you work through the design (the interfaces, the price point, the look, etc.) you’ll run these by a sampling of your potential customers. Does the design still meet their needs? How would they use it differently than you expect? What assumptions have you made that are simply not true? Through simple usability testing and conversations with your customers, we’ll teach you how you can make sure you still have a covetable product they’ll love.