Product Design
Learn what this engagement looks like across scope, timeline, deliverables, and how we'll work together throughout the entire project.
Product Design Overview
We'll examine your solution or service and where it needs to go from where it is right now. I want to understand the experience, what users love about it (along with what they don't), and what's at stake for the future.
Who It's For
Entrepreneurs or teams currently operating with a solid v1 or proof of concept. The validation has been important, but now the experience needs to mature and scale to reach full potential.
Length of Engagement
It's likely going to be at least 3 months. Based on your specific scenario and needs, we can structure it as fixed scope or long term engagement based on time.
What you'll walk away with at the end of the product design process.
Designs For Front-End
I'll pass off files to your team in whatever format they're needed. Each page and feature will be ready to come alive in the stack during development.
Prototypes
You'll get a reference project that anchors design and interaction expectations for the builders. They won't be the real thing, but they'll look like it.
Documentation
Interaction-based user stories and details that go beyond the prototype will be provided for reference by the dev team.
Design System
The product style guide and component library will ensure consistency as you continue scaling the experience and adding pages and features.
Support Phase
There will be fixed time included in the scope for fixes and fast follows. Needs will arise that were never able to surface during discovery, so we'll plan accordingly.
Ongoing Relationship*
We don't have to call it quits. If it makes sense to keep a steady chunk of time intact even after we've completed the first set of deliverables, I'd be happy to arrange that.
Build Partner*
If you don't have your own team to build the product and need a development partner, that's something I'm happy to work out as well.
How designing a product looks from beginning to end.
While every project is unique and exciting in its own way, this is the process you can expect as we design your product like pros.
1.
Discovery (Internal & External)
You'll walk me through your solution as it stands so I can see what you're solving and how it's working right now. I'll also talk to some users or customers to get familiar with how they experience it.
2.
Information Architecture
We'll map out what needs to change, what needs to be created, and what success looks like in the end. This will come together as a series of assets including diagrams, flow charts, and data tables.
3.
Wireframes
I'll assemble visual representations of how the architecture, layouts, and flows will be experienced in screens and sequences. These will be low fidelity (black and white, no photos or design treatment) and we'll spend a few rounds of revisions making sure they're right before moving on.
4.
Prototype
We'll move from wireframe into high fidelity designs of key screens and interactions that mirror what the real thing will look like. I'll walk through it with real users and customers to make sure it aligns with expectations. We'll spend a few rounds here getting it right before anything moves to code.
5.
Handoff / Build
If you have your own engineers, I'll remain alongside them during the development phase to ensure a smooth handoff. If you need development of the platform once the design is complete, that's an option I can handle as well.
6.
Support
Once the design is out in the wild, it's a guarantee that new needs will arise and changes will be required. I'm dedicated to supporting you as the product evolves and matures.
What I'll need from you
- Clear definitions of who your users are and what their Job To Be Done is when inside the product.
- Understanding of how the product is sold and what distribution and scale looks like
- Technical requirements for things like development stack, authentication, roles and credentials, mobile use, security, etc.
- Access to customers and users for participation in discovery and user testing.
