Direction
Define the world you want to exist before you define your organization's mission or start shipping small deliveries: without that vision, teams will move in different directions and politics will decay all ability for innovation.
An operating philosophy, engineered for execution, not consensus.
Not some list of best practices or vague advice, this wiki has research backed entries about strategy, architecture, and leadership. Written with breadth and depth from real engineers, architects, leaders, and founders.
Initiatives
Run no more than three initiatives at once, only one of them an opportunity, and put your best people on that opportunity and on your biggest bottlenecks.
Projects
Metrics
Most organizations use metrics not to measure progress, but to hide from accountability. They optimize proxies to create the illusion of momentum and velocity, while the actual foundation rots.
Objectives
An Objective is a goal with a clearly defined end state. It has a measurable outcome and/or change in output. Without an objective, teams measure motion instead of progress.
Problem spaces
One of the most important things you do is to define the problem spaces that others should occupy and solve.
Tech debt
You've likely heard technologists use the term "technical debt", but it's not clear exactly what it means or how you treat it. And it sounds really bad.
Scope
When work stalls, cut the scope before adding time or people. How small commitments and quick wins build an execution bias.