How Brightlane Labs halved code review time with preview environments
A design tooling company gave every pull request its own live URL, so designers, PMs, and engineers review the real thing.
Results
One link per pull request
- Shorter reviews
- %
- Median time from opened to merged.
- Previews a week
- +
- Each with its own database branch.
- More releases
- ×
- Compared with the quarter before.
The challenge
Brightlane Labs builds a collaborative design tool used by product teams. Reviews happened in screenshots and screen recordings, because only engineers could run a branch locally.
Feedback arrived late, often after a change had merged, and a shared staging server meant one broken branch blocked everyone else’s testing.
The solution
The team turned on preview environments for the main repository. Each pull request now gets a full copy of the stack, with a seeded database branch and its own URL posted as a comment.
Designers and product managers review the live build in the browser. When the pull request closes, the environment and its data are removed, so nothing lingers on the bill.
The results
Review loops that used to take days now close within an afternoon. The shared staging server is gone, and release frequency tripled because merged changes are already tested by the people who asked for them.
“Preview environments changed how we review work. Designers, PMs, and engineers all click the same link and give feedback on the real thing.”
