Managing Inputs vs. Managing Outputs

Managing Inputs vs. Managing Outputs

Lots of managers talk about how they are focused on results and care less about how much time you spend, etc.

The problem comes when members of their team do not bring results. Then often they immediately jump to conclusions like… the person is not focused enough or they do not work enough hours.

Such conclusions are often based on very few data points. Just some general perceptions that they have.

And when they force the person to work more hours or get more focused, it almost never helps. Why?

Because they have almost no visibility on the micro-decisions and activities that led to the bad result. Rather for them that part is like a black box.

And since they don’t understand what is in the black box the only conclusions they can make are these very general ones that are typically wrong.

Today i’m going to explain further what I mean.



The ‘Black Box’

By the ‘Black Box’ I mean when a manager does not have transparency on the decisions that a team member took each day. And therefore they cannot input on them in a timely way.

They also do not have visibility on what progress was made on each prioritised topic each day. Nor do they see if the person worked on any non-prioritised topics.

Rather the manager relies on two interactions typically:

  • Some type of regular catch-up like a weekly one-on-one

  • A direct message from the person (eg. via Slack) when there is an issue that the person wants help on (which tends to happen sporadically).

Therefore everything else that happens outside of these two interactions is what I call the ‘Black Box’. And in my experience, this is where most of the work was actually done.



90%+ of managers I have seen operate via this ‘Black Box’

Almost all managers operate with this ‘Black Box’ approach. They have one-on-ones at some regular interval and outside of those they don’t really hear much from their team members. Except when problems occur.

And note that this is normal.

This is how most managers were taught to do the job.

This is how some of the ‘best managers’ out there operate. You know… the guys that write all the books on how to manage.

So how could they possibly be wrong?

And how could this guy Ken, who obviously is not nearly as well known as them, possibly be right?

Well my answer to that would be try it and then tell me i’m wrong. What i’ve consistently found is when people use these systems themselves correctly, they become almost instant converts.

I don’t need to convince them this stuff is better. They convince themselves and then start telling me just how much more shit they are getting done.



How do you open the ‘Black Box’?

So how do my systems open this ‘Black Box’?

Well think about it.

Literally everything is a task. And all work is reflected as an update to a task (as comments).

So you know in the comment history of a card every time a person worked on the card and what they did.

You know why they got stuck. And responded almost real-time trying to unblock them.

So if they end up failing at something I have a very strong understanding of why they did. And I do not need to make vague recommendations.


Rather I can make very specific ones, which I’m doing almost real-time each day.

So how do they ‘fail’ in my system? Well there are really only two ways:

1- They don’t follow my system (in which case they are off the team)

2- They are not capable of doing the job

That is all! And that makes it pretty hard to fail actually.

Compare this to the ‘traditional’ system where I often find that the number one reason people fail is because of poor alignment with their manager.

For example they misunderstood what their manager wanted and then went off in the wrong direction, which ends up frustrating the manager. Then the relationship gets damaged and it’s all downhill from there.

This happens all the time!



So the reality is… to consistently get the right outputs, you need to manage the inputs!

Pretty much all of the managers i’ve seen in my career who said that all they cared about was the outputs did not scale well.

Why? Because managing in that way relies on getting very high quality people consistently and forming a trustful relationship with them.

But guess what? Getting high quality people takes a lot of time and money. And forming a trusting relationship with people also takes a lot of time.

The reality these days for most managers is that they do not have these comforts.

They need their teams to deliver high quality work immediately.


If they hired a person that is not optimal for the role… most managers just need to suck it up and deal with it. Because they don’t have time to change the person.

And so to deliver consistently with these limitations, you absolutely NEED TO BE MANAGING THE INPUTS.

I’ve seen this proven to be the case so many times that I consider it a law rather than my opinion.

And if you use a system like the one I propose… your ability to ‘manage the inputs’ will improve exponentially. Making it a no brainer in my humble opinion.


These are the systems we use with our freelance teams at www.taskbeasts.com.

Where the vision is that you can outsource pretty much anything in a cost efficient and flexible way using a single, streamlined process. We call this the 'Beast Method'.

If you're interested in scaling your company in a way that is far more flexible and cost efficient than the traditional route of hiring employees... DM me to find out more.

Carsten Ley

Strategy & OKR Coach ??Transformation, PMO & CX Leader??Ex Deloitte | Citi | Lazada ??TedX Speaker & Podcast Host ?? Lego Innovation & Play Coach ??Uni Lecturer & Mentor

6 个月

Actually we say that in OKR consulting that only outcomes or results count, but we also make sure they have an underlying task and action process to be clear on how to reach or replicate results. Newbies or less skilled people we keep on action rather than result responsibility and give them time to understand or build systems

Yann A?tBachir

AI @ Google | I share Career Tips in Tech | 2k+ Newsletter Subscribers

6 个月

Ken Leaver, you make a great point about focusing on managing inputs rather than just outputs. It's true that when you have visibility and control over the inputs, it becomes much easier to guide the process, make timely adjustments, and ultimately influence the outcomes. ??

Susan P. Chen, Ph.D.

Fractional CHRO & Keynote speaker | Leads co:grow on a mission to transform HR in the start-up ecosystem | Certified Coach & StrengthFinder Facilitator | Angel Investor | Author of "The Death of Best Practices".

6 个月

Agreed that teams often forget to build a “system” and just focus on putting out the daily fires. Building a system and getting out from the blackbox mode require “intentionality” - which is tough when companies are growing at scale. Thanks for the very articulated sharing!

要查看或添加评论,请登录

Ken Leaver的更多文章

  • Why prioritize? Just do it all.

    Why prioritize? Just do it all.

    My whole career I’ve been taught the mantra of focus, focus, focus. And if I was using the old way of managing things I…

    2 条评论
  • Containing complexity as you scale is key

    Containing complexity as you scale is key

    Reviv has really hit it’s stride. The business is growing almost too fast.

  • Fight in the arena that was designed for you

    Fight in the arena that was designed for you

    The rules of the game are very different depending on who is running the show. That is the one thing that has…

  • Why community-based businesses rock

    Why community-based businesses rock

    I’d never really run a community-based business before. And i’ve started probably 10 or more startups in the past 20…

    4 条评论
  • The dilemmas of early scaling

    The dilemmas of early scaling

    So I’m in that early period of scaling Reviv where I have way more to do than I could ever possibly get to. And this…

    5 条评论
  • The importance of iteration speed

    The importance of iteration speed

    Someone asked me earlier this week how to get people to update their Clickup cards more frequently. It was a very hard…

    6 条评论
  • Execution = Structure x Organization

    Execution = Structure x Organization

    This past week I sat through a number of traditional-styled workshops for a client and we had some good brainstorming…

  • The 'tech team on demand' model

    The 'tech team on demand' model

    I was reflecting recently on a client I’ve been working on for awhile where I set up and have been overseeing their…

  • I predict the end of bloated, multi-layered corporates

    I predict the end of bloated, multi-layered corporates

    I was talking to a friend earlier in the week who works at one of the large SE Asian tech conglomerates. He’d been…

    7 条评论
  • Optimize for iteration speed

    Optimize for iteration speed

    I had this manager a little less than a decade back who would run around the whole day going to meetings. His calendar…

    1 条评论

社区洞察

其他会员也浏览了