Read on Twitter
The products we build are typically just loops or funnels (or both).
How to use them to make better decisions and help build a better #nocode product.
Thread
How to use them to make better decisions and help build a better #nocode product.
Thread
Funnels:
Setup:
- What is the end state of success?
- What steps does the user need to do to get there?
- What are the conversations rates between each step?
Action:
- Identify the biggest problem
- Research why itâs happening
- Fix it
- Repeat
Setup:
- What is the end state of success?
- What steps does the user need to do to get there?
- What are the conversations rates between each step?
Action:
- Identify the biggest problem
- Research why itâs happening
- Fix it
- Repeat
Example: @bannerbearHQ
Visit -> signup -> create first free project -> hook up to data source -> convert to playing sub
@yongfook probably has his own version of this, and knowing where the biggest dropoffs allows him to address those opportunities.
Visit -> signup -> create first free project -> hook up to data source -> convert to playing sub
@yongfook probably has his own version of this, and knowing where the biggest dropoffs allows him to address those opportunities.
Iâm sure this is why he added templates like the ability to easily turn a tweet into a shareable image.
Itâs low friction to get working and you are learning the platform while you do it. Very smart.
Itâs low friction to get working and you are learning the platform while you do it. Very smart.
Loops:
Setup:
- What is the core action?
- How often should it be performed?
- Setup cohort analysis
Action:
- Track % users performing the core action week over week
- Build product improvements to remove friction for new users to complete the core action
- Measure
- Repeat
Setup:
- What is the core action?
- How often should it be performed?
- Setup cohort analysis
Action:
- Track % users performing the core action week over week
- Build product improvements to remove friction for new users to complete the core action
- Measure
- Repeat
Example: @getcuppaio 
Core action: virtual cuppa
Frequency: weekly
Assuming cuppa wanted to increase the % of new users who had a weekly cuppa, they can change their platform to be opt out instead of opt in.
Core action: virtual cuppa
Frequency: weekly
Assuming cuppa wanted to increase the % of new users who had a weekly cuppa, they can change their platform to be opt out instead of opt in.
Each week the platform would auto match you with someone in your designated time slot and you have to opt out of the cuppa versus today where itâs all opt in. A lot of friction for the user to schedule versus it just happening.
This tweak would signal to new users that Cuppa is a service where you meet new people weekly, not adhoc.
Cohort analysis will then show if this tweak successfully increased the % of new users having a weekly cuppa.
Something I know @thisiskp_ and @gill_works are considering.
Cohort analysis will then show if this tweak successfully increased the % of new users having a weekly cuppa.
Something I know @thisiskp_ and @gill_works are considering.
This structured and data driven approach will limit the amount of time spent on solving the wrong problem.
More so it will help attach your identity to the process, not the product itself. That is where many 1st time founders get into trouble.
More so it will help attach your identity to the process, not the product itself. That is where many 1st time founders get into trouble.
Success = looping this process.
Building this muscle will help increase a successful outcome.
And honestly itâs fun.
Please comment or DM if you have any questions, I love this stuff.
Building this muscle will help increase a successful outcome.
And honestly itâs fun.
Please comment or DM if you have any questions, I love this stuff.
