Startup MVP Process from the Design Perspective

Howdy,

After designing several software MVPs, I was writing some notes to myself about the process and it sort of grew from there. I try to advise clients I design for about the process and sometimes it's hard to get them on board. I want to use this to give them a birds-eye view.

What do you think? Too myopic? Confusing? How can I make this better?

---

A new web software product is made up of the following pieces (from the design perspective):
Branding
• Understanding Audience / Customer / Target / Niche <--- HUGE
• What, How, Who, Where, Why, When
• Feel / Positioning
• Messaging / Voice - drag the meaning out and say it in a unique way
• Company Culture
• Logo / Imagery / Color Palette
• At the end of this phase you should have your public face and strategy ready
 
 Initial User Experience
• Wireframes
---- Initial Mind Map
---- Key Path <-- HUGE, basically your product
---- Onboarding
---- Fast iterations
---- At the end of this phase you should have a good idea of what you want to start building
• Prototypes (Minimum FUNCTIONING product)
---- Internal testing - actualization and revelations
---- Hallway testing (5 nearby known fresh people)
---- Guerilla (or paid) Usability testing
---- Fast iterations
---- At the end of this phase you should have a much clearer idea what your product is
 
---------- Depends on Branding/Understanding of Audience Line ----------
 
User Interface
• Look and feel
• Interaction Design
• Modular Design / Atomic Design / Component design
• Motion
• Becomes the next tier of UX
• Slower iterations
• At the end of this you should have the basic architecture and the kit to grow from
 
Marketing
• Website
---- Content strategy
---- Conversion-driven design
---- Image assets
---- Unique benefit explained
---- Value propositions
• Emails
• Advertising
• In-bound Marketing
• PR
• etc (make up your own methods) This will never end

Cheers ;)