~/.mathieu

Tag: methodology

Createdslips
slips
Keeping things simple is a skill
Createdslips
slips
Duck Feature
Createdslips
slips
Discovery requires time
Createdslips
slips
Make yourself replaceable in order to sell your business
Createdslips
slips
Premature optimization is procrastination
Createdslips
slips
Self documenting systems
Createdslips
slips
A successful infrastructure is one you forget about
Createdslips
slips
Basic documentation is a must for system administration
Createdslips
slips
Validate your business idea
Createdslips
slips
You could smoke test features
Createdslips
slips
Aggressive timekeeping in meetings reduces meeting time
Createdslips
slips
Vanity metrics
Createdslips
slips
Test the waters before going all-in
Createdslips
slips
Going too broad can hurt you
Createdslips
slips
Specialising in a niche necessary for building a monopoly
Createdslips
slips
Reaching your customer is important
Createdslips
slips
Strong relationships with the customer increase the customers value
Createdslips
slips
Effort vs value of potential customer
Createdslips
slips
Incremental development
Createdslips
slips
Founders and early involved people are important
Createdslips
slips
A startup value is not just pure profit
Createdslips
slips
Thinking out of the box is necessary for vertical progression
Createdslips
slips
Being critical of the present is important to think outside of the box
Createdslips
slips
Cohort analysis
Createdslips
slips
Core metrics
Createdslips
slips
Metrics should be meaningful
Createdslips
slips
The paid growth engine
Createdslips
slips
The three growth engines
Createdslips
slips
Viral growth engine lowers marketing costs
Createdslips
slips
A viral growth engine
Createdslips
slips
A sticky growth engine
Createdslips
slips
Pivoting
Createdslips
slips
When the business model isn't working out, pivot
Createdslips
slips
A/B Testing helps to know if a feature is valuable or not
Createdslips
slips
Features are either valuable or waste
Createdslips
slips
Build, measure, learn
Createdslips
slips
A smoke test could validate just as good as an MVP
Createdslips
slips
The MVP should just be enough to draw feedback
Createdslips
slips
The growth hypothesis
Createdslips
slips
The value hypothesis
Createdslips
slips
Customer behaviour can validate your assumptions
Createdslips
slips
Micro services should not be the default
Createdslips
slips
Software should be delightfully boring
Createdslips
slips
Mocking factories should be used when mocking test data
Createdslips
slips
Unit tests should be easy to read
Createdslips
slips
Test names should be straightforward
Createdslips
slips
Validated learning
Createdslips
slips
Sustainable business model
Createdslips
slips
Finding a business model is of utmost importance for startups
Createdslips
slips
Startups should be flexible
Createdslips
slips
Startups cannot predict the future
Createdslips
slips
Complex problems might lead to over engineering
Createdslips
slips
Over engineering is bad for a project
Createdslips
slips
Fully implementing unknown tasks can be bad