Founder MindsetEmerging Pattern

Allocate protected exploration time for builders to innovate beyond assigned work without metrics

Q: How many founders have validated "allocate protected exploration time for builders to innovate beyond assigned work without metrics"?

1 founder has proven this pattern works. Examples include Michael Lopp (Slack Engineering).

High-performing engineering cultures give builders dedicated time (roughly 20-30%) for self-directed exploration. The key is recognizing these efforts without formalizing them into programs with accountability metrics, which kills the spirit of innovation. Simply acknowledge good exploratory work with 'keep doing this.'

When to use

When you want to encourage innovation but formal innovation programs feel too bureaucratic or when engineers seem stuck in execution mode

Don't do this

Creating formal innovation programs with metrics and accountability that transform exploration into another work obligation

1 Founder Who Did This

Slack Engineeringby Michael Lopp

Advocated for allocating ~29% of engineer time to creative exploration ('wolf time') without tracking or measurement, learning from failed formalization attempt at Palantir

Result:Engineers innovated organically when given unstructured time, but innovation died when the same practice was operationalized with project management oversight