Grasp any change in your codebase

Too many pull requests, architecture breaking changes, everyone's shipping faster.

Keep your self in the loop

problem.md

Whats going on?

Even 3-person teams lose track of others's changes. Pull requests were built to review one change at a time.

PR volume is so high that its complex to connect the dots until it breaks. Too fast to fully understand the changes our peers make.

At lightspeed development, we need a way to understand the bigger picture, across the team and the org.

activity

api-auth: refactored by @maria, 5% org awareness

billing: API contract changed by @lucas, silent merge.

(...) 3 more changes this week, 37% org awareness avg

vision.md

Know what shipped without reading every diff, without pinging your teammate or waiting for the next all-hands to find out.

Review at your own pace to understand the bigger picture. Across the team, the org and your peers.

Keep traceability of all the changes that matter and run tech strategy reviews over the the day-to-day changes.

digest

Org Level: 42 PRs shipped (±3mins)

Team Level: 6 PRs shipped (±2min)

Followed peers: 14 PRs shipped (±1min)

Catch up now.

execution.md

You need the context, intent and blast radius of your codebase changes so you can fully understand the changes and connect the dots.

Identify weak architecture implementations before they become problems and follow the traces to react in time.

Receive a brief to get up to date on your codebase deliveries. Choose format, frequency and delivery method.

digest

What happened last week was:

Org Level: [Playlist (±3min)]

Team Level: [Playlist (±2min)]

Peers Level: [Playlist (±1mins)]

join.md

Become aware of everything your team ships. A big picture understanding with a short time investment.