The Distance Leadership Creates

A leader sitting with two employees at a shared table, reviewing work on a laptop.

How leaders can understand employee experience by observing everyday work and examining the conditions behind performance.

By Geneèn Wright, Workforce Strategist and Organizational Anthropologist


The calls usually happened late in the day, after the last meeting had run over. As Chief People Officer, I kept a short list of HR leaders I could phone when a decision sat heavy. These were people who knew what the role asked of you without needing it explained. We traded notes on restructures, on leadership teams that wanted answers before the data existed, and on the particular quiet that follows an announcement you helped write. I would hang up feeling understood, and I came to rely on that feeling more than I realized at the time.

Those calls rarely told me anything new. We were describing the same view from similar chairs, so we tended to confirm one another’s read of things. The view from the work arrived later, and it came from a group of caregivers.

We had introduced a half-day policy to give people more flexibility. The caregivers showed me what it required in practice. A working parent who needed two hours for a child’s doctor appointment now had to take half a day to cover it, so a policy written to create room was using up time people couldn’t spare. I’m a caregiver myself, and I approved that policy without seeing the caregiver issue. My version of caregiving came with more flexibility and vacation time, so the half day looked generous from my chair. It was a gaffe, and one I could walk back. We replaced the half-day requirement with personal hours, so adults could manage their own appointments an hour or two at a time.

That is what I mean by loneliness at the top. It grows in the distance between where decisions are made and where they are carried out. A leader can receive regular updates and still have limited understanding of what a decision requires from the people doing the work.

Peer conversations gave me somewhere to discuss the demands of leadership, but understanding employee experience required time with people whose working day was shaped by those decisions. Both belonged in how I led employee engagement, and together they closed the distance between the framework and the work.

What Lorena Hickok’s 1933 Field Reports Teach Leaders

In my work, I often return to Lorena Hickok’s field reports from 1933. Harry Hopkins, who headed the Federal Emergency Relief Administration, sent Hickok, a former Associated Press reporter, around the country to learn how people were getting through the Depression and what they were experiencing as they sought relief.

That October, in North Dakota, Hickok went to see a farmer she’d been told was a “chronic kicker.” She found him doing the family washing. Since his wife died, he’d been farming and raising eight children. He’d asked if his fourteen-year-old son could take his place on a road crew doing relief work. When he went out to work on the road, he told her, things fell apart at home.

In her report to Hopkins, Hickok described what she’d seen and what she still wanted to check with officials in Bismarck. The question I take from that encounter concerns how relief work was organized. What would make it possible for the farmer to work on the road crew and keep his household going? If other families faced the same constraint, relief officials could investigate whether a different schedule or assignment would help.

The complaint reached officials before the circumstances behind it were understood. Hickok’s visit supplied context that could change how they interpreted the problem and what they considered doing about it.

How leaders can understand employees’ everyday work

Field notes are part of my practice now, and they were part of how I worked as a CPO and people leader. Sitting in the rooms where the work took place showed me how it got done, and because I told people why I was there, I could look at a workflow with them and note where the constraints seemed unreasonable. On days with capacity to spare, a desk near the action let me hear what came up in an ordinary day, while people were working out what to do next.

People knew I was the CPO when I sat down. That was part of the room, too. The value of being there was that I could ask about something we were both looking at. People could show me what had happened before I arrived, explain why they handled something a certain way, or tell me that what I’d seen was unusual. A meeting already on the calendar and a desk near the work gave me places to begin.

For a distributed team, this might mean joining an existing working session or asking someone to walk through a recent handoff. My goal was to explain what I wanted to understand and let the people doing the work describe what my view left me blind to.

How to Turn Workflow Observations into Management Decisions

Observation becomes useful to a leader when it produces a decision someone can test. This five-step checklist turns what you see in a workflow into a change you can measure. The example is a team expected to turn around client requests in two days.

  1. Follow one piece of work from start to finish.
    Trace a single request from intake to delivery. The numbers tell you how often the team misses its two-day target. Watching one request might show you that the team finished its part by the first afternoon and spent the remaining time waiting on approval from another group with its own deadlines.

  2. Confirm the pattern across several cases.
    One stalled request is an incident. Ask the people handling requests how often it happens, then compare timing across several cases. When routine requests keep stalling at the same point, you have found a condition of the system worth examining.

  3. Name what the constraint is meant to protect.
    Approvals usually exist for a reason, such as quality, risk, or a client commitment. State that purpose before changing anything, so the fix keeps the oversight the organization still needs.

  4. Identify who has the authority to change it.
    Determine which requests the team could clear on its own and who holds the authority to change the arrangement. If you control the constraint, act directly. If another part of the organization owns it, name the person you need to work with and tell the team when you will come back with an answer.

  5. Make one change and review the results.
    Agree on a single change, set a review date, and track two measures: whether turnaround improves and whether the oversight you need still holds. Report what you learned to the team that surfaced the issue.

This is where I apply pattern literacy, examining how authority, expectations, relationships, and working conditions shape what people can do. In The Modern Manager Method, that inquiry helps leaders decide what they can change directly and where they need to exercise influence.

Make employee listening part of how you lead

You can hold office hours and still set time aside to learn this way. Some things are easier to show while they’re happening. Other things, especially when someone’s manager is involved, need a private route people can trust.

In either case, people deserve to know what you understood from what they shared and what you can do with it. A concern that keeps appearing across teams deserves a closer look at the conditions those teams share. I explore how that changes a performance conversation in Beyond the Behavior.

I think about those days when my calendar was full of calls. It’s easy for the time you spend discussing the organization to crowd out the time you spend with people doing the work you’re discussing. Some of that time belongs on the calendar, too. Start with a decision you helped make about how people should work. Where could you spend an hour this week seeing what it takes to carry it out?

If your managers keep encountering the same obstacles, explore how I work with organizations to examine the conditions behind them and design a response.

Further Reading

Geneèn Wright

Geneèn is a Workforce Strategist and Organizational Anthropologist, founder of Geneèn Wright HQ, and creator of The Modern Manager Method. She uses labor history and pattern literacy to help professionals and organizations read the systems that shape their work.

https://www.geneenwright.com/about
Next
Next

The Management Read: How Modern Is Your Management?