Too many startups focus on feasibility first. They love building, so they build.
Too many corporate innovators focus on viability first. They need to prove (on a spreadsheet) that the business can be big enough.
Both are usually a path to failure.
Ben Yoskovitz on Twitter https://twitter.com/byosko/status/1634979420195749891
yep. good point.
for internal/enterprise programs I share the "EASE" rubric for designing/building/maintaining services/APIs:
- Effective : does it do what it was intended to do?
- Available : does it do it wherever it is needed?
- Scalable : does it do it whenever it is needed?
- Efficient : does it do it in an optimized manner
Resilience is not part of the acronym but falls in there along with availability and scalability.
but, as you say, for startup products the rules are diff.
and the EASE pattern leads you to focus on "important" things first. that also means you can stop any time.
for example, you may not need it to be efficient, just effective.
if it is a job you're running locally, not used by anyone else, it may not need to scale well and availablility is easy (you have it!).
i think most of this still makes sense for startups/products but have def. gotten arguments on this list in the past<g>
Mike Amundsen
Incident Creator ❎