Read on Twitter
The best startups move the fastest. Some practical tips we picked up on fast execution @cyteracellworks:
1. Be “ruthlessly unscalable” - @patrickc
Deliver each bit of value to users as fast as possible - even if it means having a human in the loop.
Ignore scaling concerns - focus on approaches that work at your current scale
Deliver each bit of value to users as fast as possible - even if it means having a human in the loop.
Ignore scaling concerns - focus on approaches that work at your current scale
2. Use gradients - @max_hodak
Making progress on big challenges is hard.
Having gradients which iteratively get you there, like a metric to improve, solves big challenges much faster.
https://link.medium.com/GLfL62dtt7
@SpaceX Grasshopper was great example:
Making progress on big challenges is hard.
Having gradients which iteratively get you there, like a metric to improve, solves big challenges much faster.
https://link.medium.com/GLfL62dtt7
@SpaceX Grasshopper was great example:
3. “Handbook first” documentation - @gitlab
Document approaches in a company-wide, single-point-of-truth handbook.
Otherwise, team members re-ask for same info, creating “a torturous loop of interruptions, meetings, and suboptimal knowledge transfers” https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/
Document approaches in a company-wide, single-point-of-truth handbook.
Otherwise, team members re-ask for same info, creating “a torturous loop of interruptions, meetings, and suboptimal knowledge transfers” https://about.gitlab.com/company/culture/all-remote/handbook-first-documentation/
4. Written memos vs slides - @JeffBezos
Great meetings are about discussion, not information-transfer.
A written memo can be read before a meeting, keeping meeting just to discussion. Also, memo writing forces you to think through every step of logic! https://blog.usejournal.com/writing-docs-at-amazon-e025808616bd
Great meetings are about discussion, not information-transfer.
A written memo can be read before a meeting, keeping meeting just to discussion. Also, memo writing forces you to think through every step of logic! https://blog.usejournal.com/writing-docs-at-amazon-e025808616bd
5. Asynchronous discussions vs meetings
Asynchronously collaborate on a Google Doc memo before meeting, including laying out approaches in full detail.
Once no more progress can be made on the memo, a quick meeting is held with the collaborators to make the final decision
Asynchronously collaborate on a Google Doc memo before meeting, including laying out approaches in full detail.
Once no more progress can be made on the memo, a quick meeting is held with the collaborators to make the final decision
