Speed And Steering: Make Room For Both In One-On-Ones You Run
Aditi Khullar, VP at Two Sigma, senior engineer bridging research to production; experience leading AI/ML teams.
gettyWhen my dad taught me to drive in an empty parking lot, he gave me only two pieces of advice: Watch your speed and look where you want to go.
The same holds true in engineering management, except the lot is never empty and everyone else is driving, too. Here, the questions you ask are your biggest tool. They set the team’s speed and the direction of its mission, and they come in two kinds. Momentum questions (how and when) control the speed, moving the work along a path already chosen. Direction questions (what and why) do the steering; they set priorities and, when needed, force a pivot.
For years, I asked both kinds in the same one-on-one, and I always gravitated toward the momentum questions. My own sense of urgency, and my team’s drive to get things done, kept pulling our conversations toward one more blocker to clear. The direction questions, which could slow things down, kept slipping to next week. So, I split the hour in two: the first half for momentum, the second for direction.
Andy Grove made the case for a full hour decades ago, because the harder topics rarely surface in the first twenty minutes. I recommend you protect a full hour with each report, every week, and give each kind of question its own protected time.
The first part of a one-on-one is about the work in front of your team. Follow their lead and keep it moving: what is blocking you, what do you need from me, how will you test it, when will it land. These questions clear the road and, asked consistently, teach people to ask them of themselves.
They help you as much as it helps them. As Alison Wood Brooks and Leslie John found, questions like these surface risks while they are still easy to fix and give you an honest picture of where the work stands, so you can escalate early and report the status with confidence.
Speed only helps if you are heading the right way, which is where direction questions come in.
This is where you steer, and where you get to know the person you are steering with. As you grow more senior, you earn more license to nudge, direct and, when it matters, drive.
One engineer wanted to grow into a new role, so I chose projects to build those skills. With another, I was honest about how their pace was being perceived and what it could mean for their trajectory. These conversations build trust, because people see you have their interests at heart. The more often you have them, the fewer hard ones you need, and the easier those land.
Skip the direction questions, and what drives a person never gets discussed, and their growth is left to whichever project lands on their desk. Protect this time, and you can match people to work that stretches them, so they grow and the project gets their best.
It is worth noting, however, that some things don’t fit either half. A strained relationship with a teammate, or a hard time outside of work, can matter more than any deadline. When that happens, let the hour make room for it.
The split matters more than the schedule, and the two parts do not have to run on the same rhythm.
During a delivery push, momentum may need a weekly beat while direction moves to every other week, and skip-levels and quarterly reviews can carry the bigger direction questions. What matters is that direction has a protected place somewhere, even when it is not every week.
The balance also shifts with seniority, or what Andy Grove called task-relevant maturity. With junior engineers, the discussion often gravitates to momentum questions, because asking how they will test a change, week after week, is often how they learn to ask it themselves. Senior engineers already ask those questions, so their hour moves toward direction, and too many momentum questions aimed at them could be perceived as micromanagement. Google’s Project Oxygen found the same, with engineers disliking technical micromanagement but welcoming close attention to their careers.
Engineers shift from momentum toward direction as they grow. Teams don’t. They need direction questions at every stage, and only the question changes. A new team needs, “What are we building, and why?” A mature team needs, “Is this still the right thing?” to catch the drift of running on autopilot.
Whatever the mix, the direction questions are where you learn both where the team is heading and where each person fits in it. So, before your next one-on-one, don’t ask what you need to cover. Ask whether you are there to increase the speed or to change the direction, and give each its own portion of the hour.
The views expressed herein are the author’s own and do not represent the opinions, positions or strategies of the author’s employer or any of its affiliates, employees or officers. This article is for informational purposes only and should not be construed as professional, strategic or investment advice. References to specific companies, products or technologies do not imply endorsement or any commercial relationship.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
