Robert Ross
  • Home
  • Connect
  • Working with me
  • Working with LLMs

Purpose

This document is intended to make it easier to work with me by clarifying how I communicate, make decisions, manage priorities, and respond to disagreement.It is descriptive, not prescriptive. It reflects how I tend to operate, where I am effective, and where others may need to compensate for my weaknesses.

Scaling People

The idea for a “Working With Me” document comes from Claire Hughes Johnson’s Scaling People: Tactics for Management and Company Building. Hughes Johnson recommends that leaders document how they operate so that colleagues do not have to infer their expectations, communication preferences, and decision-making style through trial and error. I have adopted the idea because I believe management improves when expectations and working practices are made explicit. This document should therefore evolve as I receive feedback and better understand the difference between how I intend to operate and how others experience working with me.

How I Think

I tend to think in systems. I am usually trying to understand:

  • What problem we are actually solving
  • Whether the proposed solution addresses the root cause
  • What incentives or structures are producing the current behavior
  • Whether the work will remain useful and maintainable
  • What tradeoffs are being made, including the ones that are not being stated explicitly

I am skeptical of activity that is mistaken for progress. I care less about whether work appears busy and more about whether it produces a meaningful, durable outcome. I often challenge the framing of a problem before discussing the solution. This can feel slower at the beginning, but it is intended to prevent us from solving the wrong problem efficiently.

Harris School of Public Policy: “Social Impact, Down to a Science”

The University of Chicago Harris School of Public Policy’s motto—“Social Impact, Down to a Science”—captures an important part of how I approach public-sector leadership. Public institutions should pursue meaningful social outcomes, but good intentions are not enough. Decisions should be grounded in evidence, clear reasoning, disciplined implementation, and an honest assessment of results. This does not mean that every important question can be reduced to a metric or model. It means that public impact should be approached rigorously: define the problem, test assumptions, measure outcomes where possible, acknowledge uncertainty, and revise the approach when the evidence changes. The phrase also reflects how I think about data and technology. The purpose of technical work is not technical sophistication itself. It is to improve the institution’s ability to make decisions, deliver services, and produce better outcomes for the public.

Prioritization

My approach to prioritization follows a simple principle: meaningful impact requires disciplined choices. I generally prioritize work based on:

  • The significance of the outcome
  • The strength of the evidence that the work will produce that outcome
  • The cost of delay
  • The risks created by not acting
  • Whether the work advances an agreed strategy
  • Whether it creates durable value rather than a temporary fix
  • Whether the organization has the capacity to execute it well

I take tradeoffs seriously. Every new commitment displaces something else, even when that displacement is not acknowledged. I am therefore skeptical of work that is presented as urgent without a clear explanation of why it matters, what deadline is driving it, and what should be deprioritized to make room.

I also distinguish between visible activity and actual progress. Work should not be prioritized simply because it is easy to explain, politically convenient, or immediately observable. I prefer work that addresses root causes, strengthens institutional capability, or improves future decision-making.

This approach is influenced by the Harris School of Public Policy’s motto, “Social Impact, Down to a Science.” I interpret that phrase to mean that impact should be pursued deliberately: define the problem, examine the evidence, make explicit choices, and evaluate whether the work produced the intended result.

GitLab’s Handbook and the “Manager of One”

My approach to documentation, ownership, and asynchronous work is heavily influenced by GitLab’s public handbook. I am particularly influenced by GitLab’s concept of the manager of one: a person who can independently manage their own responsibilities, identify what needs to happen, communicate clearly, and follow through without requiring constant direction. GitLab connects this philosophy to its use of directly responsible individuals, or DRIs, who have clear ownership of specific work.

Being a manager of one does not mean working in isolation or never asking for help. It means exercising judgment, making reasonable decisions within one’s scope, raising risks early, and taking responsibility for outcomes rather than waiting to be managed task by task. My goal as a manager is not to personally control every decision. It is to build an environment in which people have the context, authority, skills, and confidence necessary to manage their own work effectively.

The Leadership Pipeline

My understanding of management is also influenced by The Leadership Pipeline by Ram Charan, Stephen Drotter, and James Noel. The Leadership Pipeline treats leadership as a set of learnable practices rather than an innate personality trait. It argues that each transition into a new level of leadership requires changes in three areas:

  • The skills a leader must develop
  • How the leader allocates time
  • What the leader values and considers important

A person who becomes a manager cannot simply continue doing their previous job while adding supervision on top of it. The work itself must change. Similarly, managing managers requires a different set of behaviors from directly managing individual contributors.

This framework affects how I evaluate both myself and other leaders. Leadership performance should not be treated as fixed. It can be observed, discussed, practiced, and improved. At the same time, advancement into leadership should require evidence that someone is prepared to make the necessary changes in skills, time allocation, and professional values.

How I Work

I am ambitious, impatient, and strategic. I am usually thinking beyond the immediate task toward what the work could become, how it fits into a larger system, and whether it can create durable value. I am rarely satisfied with solving the same problem repeatedly when the underlying structure can be improved.

My ambition can be useful. It pushes me to set a high bar, take on difficult problems, and pursue changes that may initially seem larger than the organization is ready for. It can also create problems. I may define the scope too broadly, move too quickly from an immediate issue to a larger strategic question, or underestimate the time and attention required to bring others along.

I am impatient with unnecessary delay, unclear ownership, avoidable manual work, and decisions that remain unresolved after the relevant information is available. This impatience often helps create momentum. It can also make me appear more frustrated or dismissive than I intend. I tend to communicate with conviction. At times, I can be long-winded or bombastic, particularly when I care deeply about the issue or believe an important principle is being overlooked. I may use strong language or broad framing to make the stakes clear.

This style can help people understand the larger significance of the work. It can also obscure the immediate point, make a tentative idea sound like a settled conclusion, or create more intensity than the situation requires. You should feel comfortable asking me to:

  • Get to the point
  • Separate the immediate decision from the larger argument
  • Clarify whether I am thinking aloud or giving direction
  • Narrow the scope
  • Slow down
  • State the specific action I want

I do not take those interventions as disrespectful. They usually make me more effective.

Communication

I prefer direct communication. I would rather hear a clear disagreement than vague agreement followed by weak execution. You should tell me when:

  • You think I am wrong
  • I have not made a decision clearly enough
  • My expectations are unrealistic
  • I am creating conflicting priorities
  • I am moving too slowly
  • I am overlooking an important risk
  • You do not understand what I am asking for

I do not view respectful disagreement as disloyalty. I view it as part of good professional judgment. I also value concise communication. Start with the main point. Context can follow. For written communication, I prefer:

  • Clear headings
  • Short paragraphs
  • Explicit decisions
  • Named owners
  • Concrete deadlines
  • Links to the relevant source of truth

I dislike important decisions being buried in chat threads or left undocumented.

Meetings

I do not believe every problem requires a meeting. A meeting should have a purpose that is difficult to achieve asynchronously, such as:

  • Making a decision
  • Resolving disagreement
  • Working through ambiguity
  • Coordinating across teams
  • Reviewing something that benefits from live discussion

I prefer agendas and pre-reads when the topic is complex. I may interrupt or redirect a discussion when I believe it is drifting away from the decision or problem at hand. This is usually about focus, not about dismissing the speaker. I value protected focus time and try to reduce unnecessary meetings for the team. I am not always as successful at protecting my own calendar.

One-on-Ones

I see one-on-ones as a space for management, not simply status updates. Useful topics include:

  • Decisions you need from me
  • Risks I may not see
  • Problems with team processes
  • Feedback for me
  • Career development
  • Workload and prioritization
  • Cross-functional difficulties
  • Issues you are reluctant to raise in a larger group

Routine project status should generally be documented elsewhere unless it requires discussion. I may use one-on-one notes to preserve context and clarify what was discussed. Written documentation helps me remember commitments and patterns over time.

Feedback

I prefer direct, specific feedback. Good feedback identifies:

  • The behavior or decision
  • The effect it had
  • What should continue or change

I do not need feedback softened to the point that the meaning is unclear. I may respond to feedback by asking questions or testing the reasoning. That does not mean I am rejecting it. I often need to understand the underlying pattern before I can act on it. I try to give feedback clearly and early. At times, I may wait too long because I am still trying to determine whether something is a pattern or an isolated event. This is an area where I need to improve.

Delegation

When I delegate, I try to distinguish between:

  • A task to complete
  • A problem to solve
  • A decision to make
  • An outcome to own

These are not interchangeable. I value people who take ownership of the underlying need rather than completing only the narrowest interpretation of the assignment. At the same time, I know that unclear delegation creates avoidable frustration. If the level of ownership is unclear, ask. I do not expect people to read my mind.

Quality and Standards

I care about quality, but not perfection for its own sake. I care most about good enough, not perfect. I am particularly sensitive to work that creates future manual burden, relies on undocumented knowledge, or cannot be reproduced. I will often push for a repeatable process rather than a one-time answer, even when the one-time answer would be faster.

Product and Strategy

I believe strategy is the act of making choices. A strategy should clarify:

  • What we are trying to achieve
  • What we will prioritize
  • What we will not prioritize
  • What capabilities we need to build
  • How individual projects fit together

I am skeptical of strategies that are only lists of aspirations. I think in terms of products rather than isolated deliverables. A product has users, an ongoing purpose, an owner, and a lifecycle. A report, tool, or workflow that nobody owns will eventually deteriorate.

Conflict and Disagreement

I am comfortable with substantive disagreement. I am less comfortable with:

  • Passive resistance
  • Avoiding a decision
  • Agreeing in the room and undermining the decision later
  • Repeatedly reopening a decision without new information
  • Using process as a substitute for judgment

Once a decision is made, I expect people to execute it unless new information materially changes the situation. I also expect myself to explain decisions, particularly when I do not follow someone’s recommendation.

What Can Be Difficult About Working With Me

I can be intense.

I may move quickly from a specific problem to a broader structural issue. This can make a conversation feel larger than the original question.

I sometimes see the long-term implications of a decision before others do, but I do not always explain that reasoning clearly enough.

I can become impatient with:

  • Repeated ambiguity
  • Poorly defined ownership
  • Avoidable manual work
  • Decisions made without considering downstream consequences
  • Work that appears performative rather than useful
  • Requests framed as urgent without evidence

I may underestimate how much context I have in my head. Ask me to slow down or explain the connection.

I also have a tendency to absorb work when I believe it is important and under-managed. This can solve the immediate problem while masking a capacity or accountability issue. I am trying to become more deliberate about when I step in.

What I Need From My Team

I need people to exercise judgment. I value colleagues who:

  • Raise risks early
  • Make recommendations
  • Ask precise questions
  • Document decisions
  • Protect the integrity of agreed priorities
  • Take ownership
  • Challenge weak assumptions
  • Distinguish urgency from importance
  • Follow through on commitments

I do not expect people to be correct all the time. I do expect them to be transparent, thoughtful, and accountable.

How to Get the Best From Me

You will get the best from me when you:

  • Bring me a clearly framed problem
  • State your recommendation
  • Tell me what decision you need
  • Give me a deadline
  • Surface the tradeoffs
  • Push back when I am unclear or wrong
  • Put important context in writing
  • Tell me when I am becoming the bottleneck

Do not wait for me to infer that something is going wrong.

What You Can Expect From Me

You can expect me to:

  • Take the work seriously
  • Explain the reasoning behind major decisions
  • Defend the team from low-value work
  • Give direct feedback
  • Admit when I am wrong
  • Change my position when the evidence changes
  • Care about the long-term quality of the organization
  • Push for clarity when the easy path is ambiguity
  • Support people who take responsibility and exercise judgment

You should also expect me to continue revising this document as I learn where my self-perception does not match other people’s experience.

© Robert Ross