
Hi, I’m Brian Dys — a photographer from the inside looking out · a composer entangled in electronic music · a UX designer · a spouse, a parent, & everything in between.
In designing the user interface (UI) of an app, it is common to start with the design of the populated state of the UI. As designers, we envision perfect scenarios, common flows, and predictable results. This, understandably, contains the bulk of work a designer has to face. It contains all sorts of issues that need to be addressed.
In turn, we might neglect designing for the different states of the component or the whole system that we are designing.
In general, here are the different states a component might be in:
Groups presenting their pitch decks:
For next week, determine the valuation of the company.
Meet the VC, ask for money how much is needed for the next milestone and how much is the share you’re willing to give.
Workshop
Better communication
Communicating the message of the product/service better
Create a presentation deck
Communicate clearly about the hypothesis
Clarity is more important than certainty
Are you clear about what you know about your business today?
Huge companies spending a lot of money just to get their message to you.
Huge companies are afraid of disruptions from startups.
Acquisition Strategy
Funnel Drawing
Recap of last week’s topic: funding lifecycle
Designing the Product/Service to see Product-Market Fit: metrics is Desirability (how the customers feel about your solution? Would they recommend the product to other people, if not, why not? On a scale of 1 to 10. To see if there is a strong Product-Market Fit to the point that they would recommend.)
Designing the Business (channels, acquisitions, delivery) to see Feasibility and Financial Viability; this is where revenue will come in.
Validation stage: Learning not Earning