Agency leaders are facing a perfect storm right now. Your clients demand more value while scrutinizing every hour billed. AI tools threaten to commoditize the work your team creates. Meanwhile, your team wants to do work they care about, not just tick off tasks.
In this high-stakes situation, your response might be to tighten control or track more metrics to ensure your teamâs productivity. But Laurel Burton is choosing a different path.
At the time Burton took over as CEO of Instrument, the 300-person agency âwas in decline.â She was under pressure to turn things aroundâand in moments like that, control can feel like the only lever left to pull. âWhen things get really difficult, outdated beliefs sneak back in,â she says. âBecause on the other side of stress and anxiety, everything feels out of control.â
But Burton recognized that gripping the reins tightly wouldnât solve the agencyâs challenges. Instead, she built an environment of trust. She focused on matching talent to meaningful work through chemistry and compatibility. She carefully curated tools that enabled creativity rather than just tracking it, leaving Instrument much stronger and more profitable.
Hereâs tactical advice from Burton on building a high-performance team that delivers innovative work while maintaining healthy margins.
1. Make trust your foundation
At Instrument, trust isnât a value, itâs an operating system.Ìę
The agency is structured so that product, marketing, and design teams operate with full autonomy, like their own creative studios. They donât track time or set utilization targets. Itâs a radical modelâand a deliberate rejection of the systems that Burton believes stifle innovation. âIf you have to use time as the metric of your success, youâve already lost the brief for creativity,â she explains.Ìę
For Burton, stepping away from traditional metrics was a necessary move. In other contexts, tools like time tracking can play a valuable roleâsurfacing insights that improve margins and resourcing decisions. But for Burton, the priority was clear: restore autonomy first and create space for teams to do their best work.
Instead of billing per hour, they have a fixed rate for each project. So, their producers are entrusted to find the right teams for the right projects, balancing skills and costs to deliver on budget.Ìę
âOur producers are empowered to make the decisions. I trust them. I tell them, âLet me get out of your way. You know what you need to deliver. Play around with the hours. Itâs not science, itâs art.ââ
While trust is central, projects are not left to chance. To track the health of every project, they scenario plan in a custom tool and monitor in șù«ÍȚÊÓÆ”. This process helps ensure they do not exceed the planned costs.Ìę

đ Learn how Ìę
Lead with trustâand still protect your margins
Instrumentâs model shows that trust and structure arenât oppositesâthey work best together. When your systems support autonomy, you unlock better work and better results.
Consider doing a quick audit of your processes to help identify where you rely on tools or metrics to enforce accountability. Could conversations or clearer ownership replace some of them? Can you develop custom metrics or processes that give your team more autonomy?
The shift might be simple: replacing rigid metrics with intentional trust, backed by the right systems.
2. Create conditions for your people to thriveÌę
Your teamâs environment determines their performance. Sometimes, well-intentioned changes to these conditions can go wrong, causing your team to work less effectively and reducing their motivation.
Burton learned this lesson when she implemented a return-to-office mandate at a time when Instrument was losing its rhythm and in decline. Instead of reconnecting the teams and improving momentum as she expected, morale plummeted. When she decided to roll back the mandate, team members found ways to connect and work together organically.
Now, before implementing changes, Burton asks herself, âWould I want to work under these conditions?â If the answer is no, itâs likely a sign to rethink the policy.
Design from their perspective, not yours
Burtonâs experience is a reminder: even well-intended changes can fall flat if theyâre built from the top down. Tools, policies, and processes need to reflect how your team actually worksânot just how you imagine they do.Ìę
Leading with empathy means designing with your people, not just for them. That starts with listening. Talk to your team before rolling out new processes or toolsâtheyâll surface blind spots you might not see from a leadership seat. âMany people start to feel a little disconnected when they become leaders. You start making decisions that are no longer rooted in reality and the environment in which your team is functioning,â Burton explains.
And when a policy doesnât land? Be willing to change it. Reversing course isnât weaknessâitâs leadership that builds trust.
3. Assign work that aligns with your teamâs strengths
Agencies are under constant pressure to deliver, so they often assign work based on availability rather than fit. But Burton believes this approach leads to misaligned teams and mediocre outcomes. Thatâs why Instrument doesnât just assign people to projects based on availabilityâthey âcast talentâ based on compatibility and chemistry.
âCompatibility means you have the right skill sets and your passions align, and chemistry means you work really well with the team,â Burton explains. Itâs not about uniformityâitâs about building teams where diverse perspectives thrive, and individual strengths balance one another.
To support this, Instrument runs a âborrows and loansâ program. When a project needs extra support, like a designer for marketing, they borrow from other teamsâprioritizing both skill and interest. The producers use in șù«ÍȚÊÓÆ” to find the right mix of talent and availability across the org.

But knowing who has what skill is just the first step. Direct managers at Instrument are expected and trained to understand individual motivations and career goals. They then share this information with vertical leads to help find the right people for the right work.
Know whoâs available, know what drives them
Consider training team leads to understand what motivates their direct reports and make it part of their core responsibilities. Burton suggests usingâa deck of cards with 100 questions for 1:1sâto learn more about team members.
4. Curate tools with intention
Before reaching for something new, Instrument asks: can our current tools evolve with us?
Every tool they adopt reflects how they want their teams to work: with trust, flexibility, and a mindset of continuous growth. They expect their tools to evolve alongside themânot slow them down. Thatâs one reason șù«ÍȚÊÓÆ” remains their go-to resourcing platform: it supports how they lead, scale, and stay agile.
âI want to work with companies building tools that think about the users and different types of flexibility businesses will have,â says Burton.
Optimize before you overhaul
Before adding another tool, check in with your team: are you making the most of what you already use? A resourcing issue, for instance, might be solved by adjusting views or workflows in your current platformânot switching systems.
When a tool truly canât meet your needs, choose one that supports how your team already worksâso youâre not adding complexity to what already functions well. A focused, intentional stack also helps your team build expertise, instead of chasing the promise of every shiny new platform.
You canât control external chaos, but you can build resilient systems
Storms may be raging around your agency, and while you canât change the weather, you can create the right conditions for your team to do their best work in the midst of uncertainty.
That means making bold, intentional choices: questioning long-standing metrics that stifle creativity, replacing pressure with trust and autonomy, and choosing systems over stress. When you lead with intention, your team doesnât need to brace harder; instead, they navigate chaos with clarity, confidence, and the strength to stay on course.
We couldnât have written this without:
