There are 3 types of work that people have to do within their organization:
• Produce
• Arrange
• Impress
Suboptimal allocation of the individual’s & the group’s time across these 3 types of work begets Frustration, Politics, Dysfunctional Organizations.
An offbeat thread:
Frustration:
Managers should create clarity for each employee on the optimal allocation of their time across these 3 types of work, for their specific role within the org.
But sadly very few managers do.
∴ subjective defaults are chosen by each party.
∴ mutual Frustration.
Politics:
Politics can be defined as a latent bias towards Impress-work at the expense of the Produce- & Arrange-work needed for an optimal outcome for the organization.
This bias is rooted in an individual, but with sufficient individual influence, can spread across teams.
Dysfunctional Organizations:
In a Dysfunctional Organization, senior leaders encourage suboptimal allocation of individuals’ & teams’ time across these 3 types.
This tendency could be willful (Intentionally Dysfunctional) or a blindspot (Accidentally Dysfunctional).
Undetected and unchecked, this tendency can rapidly become a part of the “culture” of the organization.
Accidentally Dysfunctional organizations can be turned around with candor, humility, and hard work.
Intentionally Dysfunctional organizations are probably irreparable.
I’ve encountered more Accidentally Dysfunctional orgs than Intentionally Dysfunctional ones over my career & mentorship conversations.
Some ostensibly Well-Functioning orgs might be very mildly Accidentally Dysfunctional, with their leaders working very hard to fix the issues.
Now, Dear Intrepid Reader,
I hear you as you say that some definitions of the 3 types of work—Produce, Arrange, Impress—would be helpful.
Or more likely, would have been helpful 5 tweets ago. 🙃
Remember, offbeat thread.
Without further ado, let’s try to define the 3.
Produce:
Produce-work is about creating or maintaining artifacts to optimally serve the org’s stated purpose for its external stakeholders. The stakeholders are mainly customers, but they can also be partners, regulators, press, shareholders, etc.
Arrange:
Arrange-work is about creating structures & processes that enable the org to do its Produce-work more efficiently or effectively. Arrange-work does not directly manipulate the artifacts that the org produces for its external stakeholders but indirectly affects them.
Impress:
Impress-work is about creating a proxy for the worker’s impact & competence. It’s usually done by the worker, for the consumption of internal stakeholders who'll accordingly make decisions about (a) the rewards for the worker, and (b) the worker's future within the org.
Let's see examples.
Produce-work: products, eng infra, sales deals, professional services, support, project updates,...
Impress-work: self-reviews, 1:1s with manager (partly)
Note that each of these 3 types is essential in a Well-Functioning org i.e. there’s nothing *inherently wrong* with Impress-work as a type of work to be done.
At times, some employees (especially highly productive ones) might pooh-pooh Impress-work and view it with disdain.
But a small amount of Impress-work, done right & with the right intentions, is actually globally-optimal for the org. Orgs are complex beings, and it is therefore essential for its well-being that your impact on the org is well-understood, positioning you for even greater impact.
There are 2 sub-types of Impress-work:
• Jekyll-Impress
• Hyde-Impress
Benevolent leaders’ inability to precisely & consistently differentiate between them in the throes of complex ongoing org action is the primary weakness leading to Frustration, Politics, & Org Dysfunction.
Jekyll-Impress: This is the good kind of Impress-work that, when performed at the right frequency & duration, creates optimal org outcomes.
Hyde-Impress: This is Impress-work that’s usually disguised as Produce- or Arrange-work but is impure because it carries a hidden agenda.
Examples of Hyde-Impress:
• Status updates that depict greater progress than the reality
• Pushing for high-stakes meeting attendance at high-stakes meetings to “get visibility”
• Turf wars during re-orgs
• Taking on high visibility projects when others could do a better job
(additional examples left as an exercise for the reader, you KNOW you’ve seen plenty)
Alright, time to wrap up
My goal here was to create awareness of the 3 types of work, the sub-types of Impress-work, their contribution to the formation of Well-Functioning & Dysfunctional orgs, & the role that leaders implicitly or explicitly play in creating Dysfunctional orgs
I don’t yet have all the answers on this topic, but I hope you’ll consider these concepts & this lexicon in the context of your own organization. If you choose to do so, you can start with this foundation, but don’t be afraid to refine & adapt these ideas to your specific context
And if by doing so you make a breakthrough, however major or minor, please do share your approach with me and other folks around you.
There’s a lot more to learn here.
❤️
Footnote:
The original idea here of the types of work was inspired by this line in the book Principles by @raydalio.
“in most companies people are doing two jobs: their actual job and the job of managing others’ impressions of how they’re doing their job.”
Was a💡moment for me
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Lack of time is a perpetual source of stress in the product manager’s journey.
No matter how well you’ve prioritized, no matter what milestone your product has just reached, there is a near-infinite list of really important things you could be doing that you just cannot do.
There are many well-known resources & principles for managing time: systems such as GTD, “managing your energy, not your time”, prioritization formulas, Eisenhower Matrix, etc.
These are no doubt useful, but for product managers, these systems leave a lot to be desired.
Why do companies with major resources & distribution make products that are mediocre & often fail to reach their potential?
There are a handful of reasons, many of which you already know. But there is one under-discussed reason: Operators Optimizing for Optics
Thread:
To understand this, let’s start with a story.
START OF STORY
Acme Inc has brilliant, visionary founders (Alice & Bob), amazing culture, has built a well-loved product, and thereby created a business much larger than the early people (including the founders) had ever imagined.
With this growth, they’ve had to hire a bunch of Operators: leaders who are skilled in scaling process, teams, operations, and overall execution. So far so good. As the business & the customer-base grows, it is a no-brainer for Acme to tackle adjacent areas of opportunity.
Some reflections since turning on Twitter’s Super Follows two weeks ago.
800+ superfans have joined 🙌🏾
Biggest benefit:
I am tweeting a lot more freely because I know I am speaking to superfans who understand what I am about. More advanced & nuanced content. Fewer unsent drafts
Biggest surprise:
The community aspect of Super Follows has been A+ thus far.
While not a primary goal, it was 1 of my hypotheses for doing Super Follows. And it has vast exceeded everyone’s expectations. I polled folks yesterday for feedback, and community was mentioned by most
Many super followers mentioned that they are now using Twitter more frequently & are replying/sharing a lot more freely with the community than they might in public, because of shared alignment.
One super follower said it best: people writing without fear of being misunderstood
As they grow in size, teams within megacorps and startups tend to implicitly bias more towards Project Thinking and not enough Product Thinking.
Product Thinking is a mindset and a process that, once you see, you cannot unsee it.
Product Thinking, Project Thinking, a thread:
From my experience working in individual contributor & leadership roles over the past couple of decades, and from my advising work with a number of fast-growth startups, I have often seen myself and founders / CEOs / execs worry about these things:
And, having been in the trenches of product work for a large part of my career, and having managed / mentored / coached hundreds of PMs & PM Managers, I have often seen myself, and other ICs & managers worry about these things:
1) Be proactive 2) Begin with the end in mind 3) Put first things first 4) Think win-win 5) First understand, then seek to be understood 6) Teamwork & creative cooperation 7) Continuous improvement
Basically, the habits in the classic book.
I know that many Product Managers will ignore this because they want something more advanced.
They have already read Covey's book at age 23, so there's nothing more & nothing new to learn from it.
They want an edge over others, so they seek & love esoteric advice & tactics.
And yet, 9 out of 10 times when I am working with extremely smart & ambitious PMs who are struggling (not getting promoted, not getting the performance reviews they think they deserve, not executing well, etc.) it is because they have forgotten one (or more) of these 7 habits.