Learning by Shipping

products, development, management…

Posts Tagged ‘leadership

Getting (the Right) Stuff Done

S65-42424A key role of product management (PM), whether as the product-focused founder (CEO, CTO) or the PM leader, is making sure product development efforts are focused. But what does it mean to be focused? This isn’t always as clear as it could be for a team. While everyone loves focus, there’s an equal love for agility, action, and moving “forward”. Keeping the trains running is incredibly important, but just as important and often overlooked is making sure the destination is clear.

It might sound crazy, but it is much easier than one might think for teams to move fast, get stuff done, and break things that might not be helping the overall efforts. In fact, in my experience, this challenge has become even greater in recent years with the availability of data and telemetry. With such, it becomes very easy to find work that needs to be done to improve the app or service — the data is telling you right then and there that something is tripping up customers, performing poorly, or going unused. Taking action makes it easy to feel like the right thing is happening. It feels like moving forward. Everyone loves to get stuff done. Everyone feels focused.

But is the team focused on the right work to achieve the right results?

Just a little process

Two important realities represent a constant balancing act when leading a product. As a PM you are applying finite resources to market needs in the march towards product-market fit or are working furiously to maintain a competitive lead. In addition to the new features there is the work that sales or customer success needs and together those greatly exceed what can be delivered by engineering.

This problem doesn’t ever go away and is at the core of the role of product leadership — getting the right stuff done with the right priority.

In every well-run company there is a strong tendency towards action and a strong dislike (tending to revulsion) of process. In practice, the absence of a process is just as much of a process, just one without clear lines between action and result. A little bit of process (aka product management) can go a long way to having real focus and getting the right things done.

With a little bit of process, everyone on the team can have:

  • Shared views on what success looks like
  • Clear understanding of success measures and metrics
  • Easy mechanism to decide what should be cut or pushed out when things aren’t going as planned
  • Visible alignment between what work will impact what elements of success and which measures
  • Honest accounting of resources going into what big picture initiatives
  • Ample opportunity to participate in deciding what gets done and when

It is very easy to overdo process and go from a helpful tool to a burden people run away from. A personal goal has always been to be as lightweight as possible and to have a way of thinking about these needs that scale from projects that last weeks, months, or even longer.

My guiding principle or golden rule of process is to never ask for something from someone that does not directly help them to get their own work done. Process is not about reports or “management”, but about making sure the work each person does is the most important work to do and the time.

Just a little framework

When most people think of coming up with a product roadmap or plan, they think of ends of a spectrum. At one end there’s commonly the one slide version labeled with months or years and a couple of bullet points at varying levels of granularity and decreasing accuracy as time goes on. There’s also the detailed and long-term strategic plan that most people can’t read through that is often the work of consultants or staff at big companies.

There’s something in between that I’ve found very helpful in terms of framing the product roadmap.

The roadmap can be represented as a hierarchy of increasing detail. It starts with a mission covering years of aspirations for the whole company. From the mission follow the goals representing the 12 months of work supported by specific metrics or measures and the various roles or disciplines in the company. Teams then come together to work on projects (or milestones in a longer term project) that take weeks and are delineated by releasing product or programs to the market. Supporting the creating of projects are the day to day tasks at the feature level representing the work of individuals.

Throughout this whole system there is ongoing telemetry that is called upon to support the company with reliable data upon which to make decisions.

Mission

Whole books have been written about mission statements or the process of developing a mission statement. Nothing makes me groan more than the idea of having a meeting to craft out a mission statement. We’ve all seen the results of these efforts that are an awkward combination of passive voice, comma splices, and breathless language. Companies exist for a reason and that’s the mission.

Missions are aspirational and guide you for years and represent the reason for being. Everything you do should aim towards your mission, and how you do that is the work of the rest of the framework. Missions boldly stating that the goal is to “disrupt” tend to be a bit backward looking or focus on the mechanism versus the outcome. Rather a mission that defines a future state of being or a new world view are often the most enduring and more positive. The most important thing about a mission is that there is just one and it endures. Mission statements are best able to be expressed on t-shirts, or something close.

Goals

Most everyone thinks they already have goals. Too often though goals are expressed as metrics or scorecards, like be the most downloaded app or number, daily users, or bookings. These are easy to express and are the lifeblood of a startup. The challenge is they change frequently. Like any good code when faced with something that changes frequently, the best bet is to add a level of indirection. A goal is the abstract view of metrics or measures.

Goals are strategic concepts such as retention, ease of use, acquisition, manageability, scale, success, and more. Through evolving telemetry you develop metrics to support the goals.

By using these abstractions you might come realize you have more goals than engineers (or marketers, success partners, etc.) or that you end up with every person working on too many goals. This is part of the process of being focused about goals. For any one product there can only be 3–5 goals and those fit on one “slide”, which includes the full spectrum of engineering, sales, and customer outcomes. This is a deliberate attempt to put in place some constraints up front.

Goals are then measured in specific ways over time. Metrics are then the lifeblood of goals. Your goal might be acquisition, but the metric might be a specific mechanism of retention for a period of time; or your goal might be to improve scalability of the service but the measure might be compute usage for some time and then storage usage for another.

When thinking about goals, they almost always fall to a specific function (or role) on the team such as marketing, sales, or engineering. Having a full accounting of the goals and the associated metrics allows you to understand what will change as the team’s work progresses — what is measured will be what changes.

Projects

Projects are easy to understand — they are the releases or programs customers and the marketplace use and hear about. A project might be, for example, a full update to the service, the app, a new entry to the market, a launch, a campaign, or a major infrastructure change. Early on it is trivial to name the projects for a company. Very quickly, however, the number of projects can balloon and become increasingly difficult to track (and potentially to justify). There are SDKs, enterprise tools, segment campaigns, apps for different platforms or support for different browsers, and more.

The key reason to maintain a clear list of active projects is because momentum in continuing some project, failing to re-allocate resources, can often be the biggest constraint in getting the important work done. It common to find yourself in the situation of maintaining a project that no longer fits with the immediate needs but there’s inertia that makes it hard to change. The most important task for product management is to make sure everyone is aware of the projects being undertaken. The more the company scales the more critical it is to know what projects are active and what commitments the team is making to those. Even in the biggest companies, there are just dozens of meaningful projects.

A project has an ending date or deadline date — not a month or a quarter (those are 30 or 90 dates) but a single date — and everyone knows when the project releases or is complete.

Tasks

When you work from mission to goals to projects, the most concrete expression of work on the team is the task. A task is the actual code to be deployed, whitepaper to be written, SEO tools that will be employed, launch event to hold, features that will be designed, and so on. While a few people might care deeply or contribute to the mission, and executives generally focus on goals, and managers live whole projects, everyone is invested in tasks.

Tasks are defined by those that will do the work and those same people (or person) will decide how long it takes. Every person contributing to a project might have dozens of tasks. Tasks should be from 1/2 to 2 days — less and the accounting is too painful and more and it is likely the work is not understood enough to reliably schedule.

There are two main benefits from spending the time to create a list of work items. First, the project overall becomes increasingly predictable which is important because of dependencies (such as front end and back end, or marketing activities). Second, when things aren’t going as well as planned there is a clear view of just how far off things are along with a pre-computed list of potential savings to be had by cutting different tasks. Whether it is Asana, Trello, Sheets, Jira or more the key is just having a system that goes beyond post-its around a monitor.

What is often overlooked is how much more effective everyone is when they know the why behind the what. Everyone will do better work if the worklist flows from specific projects which have goals that are measured in a particular way. Much of the work of this framework will prove to be making the connection from task all the way to mission.

Telemetry

One additional element that permeates all of your efforts is telemetry.

The most successful organizations are also fully instrumented organizations. Everything about code, customers, and overall engagement has telemetry.

Keeping an open mind and open eye to a whole variety of measures is super important. Just that as a matter of scale and operation, you cannot hold everyone accountable or change what is being done in response to every measure. If you’re learning something that concerns you then dig in. Maybe you’ll change your plans. But when you do need to change your plans you can do so in the context of an overall framework, not just single data points.

The combination of a framework and telemetry makes it possible to more globally maximize your return on investment. Telemetry alone risks a more local optimization. A framework by itself is just guessing.

It might seem like doing all this is just too much busy-work. There is an investment to be made. Most of the effort, however, will involve “editing” or “culling” from a list that was already too long or contained a lot of things not getting done. The most time intensive work is in creating the task list and is often the most disliked or difficult to make concrete. Everyone seems to have a feeling for what work needs to be done but resistance to putting it out there. The essence of an accountable organization is taking the team through this framework and making it part of every day work.

Just a small tool

There’s a payoff to all of this that is incredibly important. If you stop here all you’ve really done is document things going on. What is really important is that you assemble information so you can have a system in place to deal with change — unexpected failures in the market place, gain or loss of people on the team, new opportunity in the marketplace, or demands from a customer. Maintaining this information in a simple tool provides the product manager with that.

There’s always too much to do, so by definition we know we are not doing everything we can to be successful. Do we know if everything we are doing is essential to the success we hope to achieve?

Seems like a simple question. In practice this is an exceedingly difficult question to answer at any given time and even more difficult question to answer over time as conditions change. In fact, I might argue it is close to impossible and that the best measure of success is to view the efforts overall as a portfolio. Just like a portfolio, however, you need to spend time digging in to understand at a more granular level where you can do better. Failing to do so too often prevents us from ongoing evaluation of work to make sure it is really helping — if there is more work than can be done, the easy path is to just assume everything going on is helping. That’s not true though!

What is suggested below might be simplistic or you might believe you’re already doing all this and more. I’ve found that most projects, especially before product-market fit, can benefit from a more systematic view connecting work to projects and goals supporting the company mission.

My own experience is that this can be accomplished in a surprisingly straight-forward manner. Doing so illuminates the work of the team and provides a great tool for the shared and ongoing management of the team.

Let’s just assume we’re working with a spreadsheet, simply because we’re going to do some math with the data. Feel free of course to use any structured tool that supports features such as collaborative editing, group-by reports/pivot tables, filters, and some basic math. The specific tool isn’t important and should not be the source of the first debate on the team!

We tend to think of the task list as a literally listing of tasks such as Implement OAUTH, Add new chart type, Create sign-up response mail, etc. Simply getting all of these done can often be helpful enough. Most tasks lists will have a name associated with the work and I’d always encourage a single name, or said differently define the task so it is the work of one person. In addition, include a column for the amount of time the task will take (0.5–2 days). For good measure I would suggest also including the date to start/finish as that allows you to use the spreadsheet to understand the relative schedule.

Then take the extra step of making sure the Project is clear. Is it for the iOS App? Does it support the SEO campaign? Is this the Beta program? Adding this label should be some simple accounting as projects are by definition distinct and represent a single release or customer/market visible effort.

The next step is key which is to add one more column which is what goal the work supports. Is this task about something like retention or scalability, for example? Avoid the temptation to think something applies to many goals or rather force yourself to commit the work to supporting a single goal. Keep in mind you already know the goals so all you are doing here is picking from the 3–5 established goals, which in turn are associated with metrics.

With that in hand you have something that looks like the hypothetical below. You can see a connection between tasks, projects, and goals.

1*q3EmMN1dWtlAzXlpcoZTUg

Keep this sheet up to date and you’re able to be ahead of the project. As simple as this seems it is just as often either overlooked or buried in too much detail to be broadly useful.

What can you do with this? There are several key sorts/filters that are enormously useful:

  • Any given person can look at their own work and know where they are and where it fits in
  • At any time, one can see how much of the time (resource) overall is going to support a given project or goal
  • Know which tasks are too far out, too big
  • Know which resources are over-constrained

And so on. This tool is the right level of complexity for projects from 10 to 5000 people in my experience. While many would love more such as dependency analysis or a task hierarchy, my experience is that is where the tool begins to overwhelm. When the tool overwhelms it isn’t used and so it doesn’t matter. (Quick note, when I first came to manage Microsoft Project I learned that the bulk of usage of the tool was not to track projects but to input a bunch of data at the start of a project just to come up with a nice-looking poster-sized Gantt chart printed out once at the project start.)

Managing projects is very difficult. While the bank account is draining and there’s a strong desire to keep moving is galactically more difficult. The fear of slowing everyone down with tools and processes is real and often justified. With so much riding on being efficient, effective, and focused it is worth investing a small amount in managing the work so as to make better decisions about what work to do and what happens when you get new information from the market.

— Steven Sinofsky (@stevesi)


Special thanks to @ProductHunt’s Ryan Hoover who took my suggested framework of Vision, Mission, Strategy, Tactics and made it much more approachable terminology. 🙌

Written by Steven Sinofsky

October 12, 2015 at 10:30 am

Posted in posts

Tagged with , ,

A Leader’s Guide To Deciding: What, When, and How To Decide

Science fiction (Star Trek) with officers sitting around a meeting table.Decision-making is one of the most difficult skills to master as a manager. A startup CEO literally sees a constant stream of decisions to be made: from hiring and firing, to Android or iOS, all the way to Lack or Billy. As the company grows to 10–20 people (usually mostly engineering) the bonds and shared experiences continue support decision-making at the micro-level. Once a team grows larger there is a need for management and delegation. While growth is a positive it also a stressful time for the company and founder/CEO.

Even for the tightest knit group with founding-team trust, the first decisions made without the CEO (or by simply giving a heads up to the CEO) are nail-biting moments for everyone. The closer the decision is to the core of the CEO experience the trickier. Deciding on UX changes or tweeting from the company account all test the ability for the CEO to delegate and the team to be delegated to.

As a company grows to having leaders and groups across different functions (heads of sales, marketing, eng, operations) the need to be systematic in delegating and deciding goes from optional to mandatory. Many founders resist this move. First founders rightfully care about everything — everything matters — and it is very likely he/she is in the best situation to make the best decision for the company. Second, founders that worked at a big company too often experienced dysfunctional decision-making and part of building a new company is to do better than that.

As a manager, I always found deciding to be both trivially easy and impossibly difficult. It is easy because like many, if you ask for an opinion from me you can get one. It is difficult because like many, the implications of sharing that opinion are not really known at the time.

For me, knowing what a decision really is about, understanding the full context of a decision, even just awareness of what is actually being decided are a few of the many challenges. Add to that all the management-speak about delegation and accountability and quickly I came to conclude I could justify any course of action. I could be anything from the center of a command-and-control decision making machine to a completely non-accountable, human-router-delegator of important choices in the name of building an empowered team.

I wrote this post in an effort to create a framework for how to think about decisions from the vantage point of a CEO/founder/exec as an organization grows beyond when the “hub and spoke” is the expected norm, and how to think about the good and crisis times when it comes to decision-making.


Deciding with Dysfunction

Making decisions is easy on paper, but a lot more difficult in practice. Worse, the more one practices the harder it is to make decisions simply because of knowing more and seeing potential downsides of just about everything. One might think experience would make things easier, and often it does, but it can slow down or even just prevent things from happening. When I was young, I could decide to drop in on a 15’ vertical half-pipe without hesitation. That was before I knew the downsides of injury (it was also before YouTube so all we had to look at for examples were photos)!

As the team grows, CEOs (and execs, depending on company size) face many challenges in getting things done or just picking the right things to do. One of the main factors is the increasing number of people involved in any choices. Deciding iOS or Android first will seem easy or “obvious” when resources are very tight and there’s no Android developer anyway.

Fast forward and consider the complexity when there is a newly hired sales leader who knows “works anywhere you do” will close deals, an engineering manager who still can’t hire an Android lead, a QA manager who is all about fragmentation complexity, or a newly hired BD lead who can choose between two partnerships but the better logo requires both iOS and Android. All of a sudden there’s no simple decision to be made and a lot of people contributing who feel their success hinges on going with their point of view. Play out over time the various potential outcomes and who is promoted, gets more responsibility, or is credited with success to see that this challenge is far more than just getting the right answer. That is normal.

As a result of people living this pattern over and over, many decision-making techniques and tools have been created. These codify a “decision making process”. In fact there is a whole Wikipedia article describing responsibility assignment matrix. These have a variety of acronyms like OARP, RACI, ARCI and more. The letters are various ways to define roles in important decisions such as reviewer/approver, recommends/consulted, responsible/accountable and more. These are tools designed to speed decision-making, clarify execution accountability, and ensure robust choices. Leaders figure out what to decide and assign various roles to participants and like magic decisions are made.

In my own experience these tools more often than not slow things down, make no one accountable, and all but guarantee compromises with which no one is satisfied. There are innumerable stories of how a well-intentioned taxonomy like the above can be used to grind work to a halt, push accountability around without establishing it, and turn a specific decision into a general battle over the meta. That’s unfortunate because making the right choices is incredibly important and having tools that add reliability and consistency to the effort would really help.

Rather than dissect a meta-process, I’d propose taking a step back and saying that the most important thing a CEO or executive must do is to keep the output and velocity of the team at the highest levels and focused on doing the right things. The first VP I worked for, way way back, hypothetically suggested “maybe a star could do the work of 3, or 5, or even 10 people” then he went on “the problem is we are doing work with 20, 40, or 50 people”. The implication of that math is clear. No matter how smart, hard-working, on top of things, or just amazing someone is, they need to work with other people and count on their work without actually doing it.

The core problem with a decision-making process starts with defining a decision and related inputs. Almost never is there all the information needed or wanted to make a choice and wait long enough then chances are context and options have changed enough to make the decision framing all wrong. So all that was really accomplished was slow everything down by simply by trying to define the decision to be made and what inputs were needed (apparently this also holds for the Federal Reserve Bank).

We know that almost nothing is made up of a single decision at a single point in time. Ask yourself how many discussions or meetings you had where you thought there was a yes/no, or a choice to be made, and after running over time the only decision was to wait, learn more, or come up with new options? It is only long after clear success or failure does the historic narrative turn into the “big decision” (and associated drama).

The essence of an agile organization is figuring out how to make fast progress against larger goals, learning and adjusting along the way. In that context, many at the company make decisions every day.


Stepping Up For Growth

With so much happening every day, rhythm is the biggest enabler of agility. If a team operates in a Flow, then everyone can do their best work. We all know what it is like to groove. We also know what it is like to have that groove interrupted by questioning the choices made or pausing to have choices validated, reconsidered, or tweaked.

Trying to get ahead of decisions sounds great. This quickly turns into trying to know what isn’t known and worse to prepare for it. Finding a way to codify the set of problems that will trigger a review or joint decision turns into a meta-planning exercise trying to agree on potential challenges.

In my experience, the real challenge is in trying to define decisions, isolate important ones, and then figure out the stakeholders for that once instance. Decisions are everywhere. Deciders are all over the place. Every identifiable decision is made up of many other choices, constraints, and stakeholders.

The following is my own idealization of the role a CEO or exec can play in decisions. Instead of kicking off a process for a single decision, spend the energy up front to decide what and how the CEO will work. Thinking this way allows for a variety of approaches for getting involved, delegating, or empowering. It avoids the complexities of figuring out what it is that is actually being decided and hairsplitting accountabilities among individuals. It introduces agility into a process rather than rigidity.

My own experience led me to believe that before I decided something that was brought to me, I had to have an idea of what role I was playing in the process. It is easy to be a boss and assume people need your wisdom, advice, or context. It can be tricky to know if you are really adding that, affirming the choices of those who work for you, randomizing them, or simply doing their job for them.

With that experience, my view is that before deciding something a CEO or exec should be clear how he/she contributes to a project or work, using one of the following:

  • Initiator. Kicking off new projects.
  • Connector. Connecting people to others so the work gets better.
  • Amplifier. Amplifying the things that are working well or not so there is awareness of success and learning.
  • Editor. Fixing or changing things while they are being done.

Let’s look at each of these in a little more detail.

Initiator

As a practical matter, assuming the organization is running at > 100% capacity then there’s a finite amount of initiating that can be done. Almost everything kicked off at the exec level looks like the strategy, new projects, new organization, or the prioritization of work. Creating or seizing new opportunities from the leadership vantage point is precisely it means to be the initiator.

  • Examples: Kicking off something entirely new (hiring process, first sales deck, new product release, opening a new position. Deciding to make a big bet on a new technology, platform. Starting a new strategic or transformative initiative.
  • Tools: Write it down in a way that someone joining the project later can quickly get up to speed. I believe writing is thinking, so taking the time to gain clarity on what to do and what success looks like only helps. Pro tip: Drafts circulated to a small set of key people, but quickly along with seeking and acting on feedback can be very valuable.
  • Granularity: Almost always this will be fairly coarse like “launch day” or “new product” but can scale all the way down to being the specific such as “add this feature”, “create a partnership”, “publish APIs”.
  • Time: When operating in a rhythm (product cycles, launches, adding new leads) initiating becomes a key part of team rhythm. About 10% of overall work is initiating new work or projects.
  • Mindset. The most important work of an exec is in kicking off a new project so put the most effort into this work product. Initiating is the only time an exec does the work of an individual contributor.

Connector

Most all decision-making challenges happen across domains. Rarely does a solid engineering leader pick the wrong toolset. Rather the toolset is wrong because the full scope of the challenge was not known. Anything crossing functional lines requires a connection. The exec is in a unique position to be constantly connecting functions and work. Helping people to know more about what is going on with others on the team while recognizing this almost never happens by chance.

  • Examples: There are classic examples across functional lines such as connecting sales and product. Many of the most interesting examples are the non-traditional ones, which can help people to gain more experience such as connecting engineering to customers. Facilitated connections rather than simple introductions afford the chance to see how parties use the connection and to drive an agenda consistent with a rhythm.
  • Tools: Presence, listening and talking have no substitutes. Even with everyone being online and available, don’t assume everyone or the right people will read everything. With any size team, the amount of “FYI” or automated information will quickly overwhelm even the most diligent. Rather than believing status reports and scorecards will connect, execs must focus on making specific connecting efforts with clear intentions to move things along. Most work has natural points where checking in makes sense. Rather than relying on ad hoc connections, use a structured approach to surface the right issues.
  • Granularity: The reason connecting is fun is because when it not randomizing or micro-managing, but simply sharing and getting head of potential problems. Connecting peers together is a service to the team.
  • Time: Spending more than half, perhaps 60%, of the time connecting is routine among CEOs and execs. A useful way to spend time is on structured, periodic checkpoints that connect the status of the current work to the start of the project. Pro tip: Most every interaction can serve as a chance to connect one part of the team to another or a CEO’s external context to what is going on internally while also using the opportunity to demonstrate listening while not trying to solve everything along the way.
  • Mindset. Connecting is the field work of the exec. Execs should be thinking about what to connect almost all of the time. Connecting skillfully is a force multiplier.

Amplifier

The CEO or exec soapbox is a super valuable tool. Within a company there are not only good things worth letting everyone know about, but lessons learned that could be shared. Since it is a given that not everything can be thought through in advance, seeing and amplifying the creative ideas or great execution seen along the way can be seen as a proxy for initiating new things. When a CEO stands up in front of the team and celebrates success or learning it just matters more.

  • Examples: The best example is to amplify the good work of the team or to turn failure into a lesson. Amplifying the good work of competitors, sales wins, or collaboration across functions gives leaders a chance to call our efforts that cross many parts of the company.
  • Tools: The team meeting is the most valuable forum for amplifying and often supporting this with something in writing (or a t-shirt or sticker!) works best. Amplifying work is also related to connecting work and often they are two sides of the same coin. The most compelling efforts to amplify are supported by great stories — when taking the time to amplify something, do so with the whole story and the background that makes it worth amplifying. It is one thing to tell people something important, but another to describe why it is important.
  • Granularity: Amplify things that apply to many people on the team but do so with a frequency that maintains meaning and impact. Pro tip: When celebrating success, execs should be sure to give the right credit to the right people.
  • Time: Execs have a unique ability to amplify success, which in turn makes this a high value effort so it is worth spending 10% of time.
  • Mindset. It is fair to view amplifying as a bit of a tax. As is often said in management, “what’s worth saying is worth repeating”. Ronald Reagan was famous for not veering off important messages because he believed even though it was old news for the press corp, it was new to those in the live audience.

Editor

In a big company, people just wish execs would go away and let them do their jobs. In a new startup, execs are doing the work (i.e. coding, selling specific accounts, designing the UX). Everywhere else many people are doing the work and the exec is figuring out when to contribute. Somewhere between “swoop and poop” and “micro-managing” is the role of contributing editor. I use the term “editor” specifically because this is about changing (or improving) the work created by others. Editing is the right of a boss, but also a privilege in a team made up of smart and creative people. Everything about editing is in how it is done. Poorly done, editing makes people feel bad and never generates the best work (except for Steve Jobs as many like to say). Done well, and editing makes everyone feel better about the collective effort.

  • Examples: Redlining a document, drilling into a design review, redoing a positioning framework, creating an outline for a blog post or release, designing the 2×2 competitive framework are all examples of editing.
  • Tools: The most important “tool” to use when editing is to do so in-person. The vast majority of editing feedback comes across as negative and critical. While there is always enough bad work to go around, finding ways to be constructive is always worthwhile. For better or worse, editing without verbal context or worse just being critical over email almost always makes things worse.
  • Granularity: Chances are the granularity of editorial input is very fine-grained. The question is not really whether to edit or not, but how many times the same thing (even for the same person) is edited. Repetition means there’s a systematic problem with communication or the people doing the work.
  • Time: Editing is a big time commitment, but not the biggest. It also comes in fits and starts. More important than time is timing. The later in the process or the closer to the deadline the higher “cost” being an editor has. Overall about 20% of exec work is editing.
  • Mindset. This is the comfort zone for every exec, especially when it is the type of work he/she did individually. The important thing is for the exec to really know the importance of the changes.

With a framework or roles like this, there is clarity in how an exec is working with the team and how work is started, iterated, and completed. I would also encourage using this framework by managers at all levels in a company. One changes the time devoted to each type of interaction.


Diving In For Saves

At this point, you probably think this all sounds well and good, but what about when things are going sideways?

When things go sideways none of this matters.

In fact, none of this really matters if the company are such an early stage that there are no more than a couple of dozen people. It also doesn’t matter if there is not yet product-market fit.

In Ben Horowitz’s Hard Thing About Hard Things, he describes the differences between a “peacetime” and a “wartime” CEO styles (specific post is here). I love his framing of decisions that pose existential questions for the company. That is a fantastic way to know when there really aren’t decision making processes other than whatever the CEO wants to do to survive to another day. Rarely are exec level choices existential at the same level, which is worth noting.

In a startup, the wartime CEO pretty much describes things until there is a solid revenue and profit stream coming from a product that works for the market. Most everything amounts to an existential choice or decision.

In an organization that is more or less working, this is a more subtle challenge. At some point few decisions are truly existential, though it turns out it is tough to know this is the case while everything is happening.

There was a recent Facebook thread among a few of the original leaders of an old Microsoft product. From the outside, most people see only the victory and to read their comments one would think it was all a cakewalk. From inside the team, every day felt existential and every choice seemed to be about the success or failure of the whole. This is the norm at big companies and explains the origin of those questionable “decision support tools”.

This all boils down to product-market fit and deciding when in fact that state was achieved. Before that time, everything is existential. After that time, most decisions are relatively minor. Unfortunately, knowing this dividing line isn’t so straightforward and the clouds of disruption always loom on the horizon. This is the fog of war in a big organization.
Operating all the time in crisis mode or thinking every choice is existential is just not sustainable as a company or leader. As fun as it seems, a whole yoga practice upside down is not a good idea.

As a company scales, the long tail of choices and decisions feels existential from within even if they aren’t. There’s no magic answer as to when one is at war or peace, even in hindsight. My view is that a CEO can decide the one thing no one else can, which is to decide things using a poorly defined process. Just keep in mind that even the most successful CEOs and execs can eventually use up that luxury and either adapt how they work or watch people leave the company.

The original generals, in the military, have evolved their thinking and modern warfare now employs the notion of commander intent as a leadership practice for just these reasons (and more). If you are interested in how the largest and most process-oriented organizations evolve, the report linked to is fascinating.

With the most robust product market fit, there will be existential moments demanding wartime decisions: a major security breach, service outage, failed sale, or losing key members of the team. Don’t ever be worried about deciding in the most top-down, non-empowered, toe-stepping manner when facing a true crisis. That’s what leadership is all about. Using the framework above, a crisis situation just demands a great deal more editorial actions.

Making decisions is something that at first comes naturally, even easily, and then as a company grows the complexity creeps up on CEOs and execs. Some of this is because with experience comes awareness of all the things that can go wrong. Most comes from the challenges of scale and decisions of when and how to let go of some things. Decision making challenges come when an unlimited amount of passion meets a finite amount of time. Taking on this challenge without introducing a mindless bureaucracy is an opportunity for a growing company.

— Steven Sinofsky (@stevesi)

Note: Also sim-published this on @medium.

Written by Steven Sinofsky

September 10, 2015 at 10:59 am

Posted in posts

Tagged with , ,

Continuous Productivity: New tools and a new way of working for a new era

with 126 comments

553698_10101017579649025_101860817_nWhat happens when the tools and technologies we use every day become mainstream parts of the business world?  What happens when we stop leading separate “consumer” and “professional” lives when it comes to technology stacks?  The result is a dramatic change in the products we use at work and as a result an upending of the canon of management practices that define how work is done.

This paper says business must embrace the consumer world and see it not as different, less functional, or less enterprise-worthy, but as the new path forward for how people will use technology platforms, how businesses will organize and execute work, and how the roles of software and hardware will evolve in business. Our industry speaks volumes of the consumerization of IT, but maybe that is not going far enough given the incredible pace of innovation and depth of usage of the consumer software world.  New tools are appearing that radically alter the traditional definitions of productivity and work.  Businesses failing to embrace these changes will find their employees simply working around IT at levels we have not seen even during the earliest days of the PC.   Too many enterprises are either flat-out resisting these shifts or hoping for a “transition”—disruption is taking place, not only to every business, but within every business.

Paradigm shift

Continuous productivity is an era that fosters a seamless integration between consumer and business platforms.  Today, tools and platforms used broadly for our non-work activities are often used for work, but under the radar.  The cloud-powered smartphone and tablet, as productivity tools, are transforming the world around us along with the implied changes in how we work to be mobile and more social. We are in a new era, a paradigm shift, where there is evolutionary discontinuity, a step-function break from the past. This constantly connected, social and mobile generational shift is ushering a time period on par with the industrial production or the information society of the 20th century. Together our industry is shaping a new way to learn, work, and live with the power of software and mobile computing—an era of continuous productivity.

Continuous productivity manifests itself as an environment where the evolving tools and culture make it possible to innovate more and faster than ever, with significantly improved execution. Continuous productivity shifts our efforts from the start/stop world of episodic work and work products to one that builds on the technologies that start to answer what happens when:

  • A generation of new employees has access to the collective knowledge of an entire profession and experts are easy to find and connect with.
  • Collaboration takes place across organization and company boundaries with everyone connected by a social fiber that rises above the boundaries of institutions.
  • Data, knowledge, analysis, and opinion are equally available to every member of a team in formats that are digital, sharable, and structured.
  • People have the ability to time slice, context switch, and proactively deal with situations as they arise, shifting from a world of start/stop productivity and decision-making to one that is continuous.

Today our tools force us to hurry up and wait, then react at all hours to that email or notification of available data.  Continuous productivity provides us a chance at a more balanced view of time management because we operate in a rhythm with tools to support that rhythm.  Rather than feeling like you’re on call all the time waiting for progress or waiting on some person or event, you can simply be more effective as an individual, team, and organization because there are new tools and platforms that enable a new level of sanity.

Some might say this is predicting the present and that the world has already made this shift.  In reality, the vast majority of organizations are facing challenges or even struggling right now with how the changes in the technology landscape will impact their efforts.  What is going on is nothing short of a broad disruption—even winning organizations face an innovator’s dilemma in how to develop new products and services, organize their efforts, and communicate with customers, partners, and even within their own organizations.  This disruption is driven by technology, and is not just about the products a company makes or services offered, but also about the very nature of companies.

Today’s socialplace

The starting point for this revolution in the workplace is the socialplace we all experience each and every day.

We carry out our non-work (digital) lives on our mobile devices.  We use global services like Facebook, Twitter, Gmail, and others to communicate.  In many places in the world, local services such as Weibo, MixIt, mail.ru, and dozens of others are used routinely by well over a billion people collectively.  Entertainment services from YouTube, Netflix to Spotify to Pandora and more dominate non-TV entertainment and dominate the Internet itself.  Relatively new services such as Pinterest or Instagram enter the scene and are used deeply by tens of millions in relatively short times.

While almost all of these services are available on traditional laptop and desktop PCs, the incredible growth in usage from smartphones and tablets has come to represent not just the leading edge of the scenario, but the expected norm.  Product design is done for these experiences first, if not exclusively. Most would say that designing for a modern OS first or exclusively is the expected way to start on a new software experience.  The browser experience (on a small screen or desktop device) is the backup to a richer, more integrated, more fluid app experience.

In short, the socialplace we are all familiar with is part of the fabric of life in much of the world and only growing in importance. The generation growing up today will of course only know this world and what follows. Around the world, the economies undergoing their first information revolutions will do so with these technologies as the baseline.

Historic workplace

Briefly, it is worth reflecting on and broadly characterizing some of the history of the workplace to help to place the dramatic changes into historic context.

Mechanized productivity

The industrial revolution that defined the first half of the 20th century marked the start of modern business, typified by high-volume, large-scale organizations.  Mechanization created a culture of business derived from the capabilities and needs of the time. The essence of mechanization was the factory which focused on ever-improving and repeatable output.  Factories were owned by those infusing capital into the system and the culture of owner, management, and labor grew out of this reality.  Management itself was very much about hierarchy. There was a clear separation between labor and management primarily focused on owners/ownership.

The information available to management was limited.  Supply chains and even assembly lines themselves were operated with little telemetry or understanding of the flow of raw materials through to sales of products. Even great companies ultimately fell because they lacked the ability to gather insights across this full spectrum of work.

Knowledge productivity

The problems created by the success of mechanized production were met with a solution—the introduction of the computer and the start of the information revolution.  The mid-20th century would kick off a revolution in business, business marked by global and connected organizations.  Knowledge created a new culture of business derived from the information gathering and analysis capabilities of first the mainframe and then the PC.

The essence of knowledge was the people-centric office which focused on ever-improving analysis and decision-making to allocate capital, develop products and services, and coordinate the work across the globe.  The modern organization model of a board of directors, executives, middle management, and employees grew out of these new capabilities.  Management of these knowledge-centric organizations happened through an ever-increasing network of middle-managers.  The definition of work changed and most employees were not directly involved in making things, but in analyzing, coordinating, or servicing the products and services a company delivered.

The information available to management grew exponentially.  Middle-management grew to spend their time researching, tabulating, reporting, and reconciling the information sources available.  Information spanned from quantitative to qualitative and the successful leaders were expert or well versed in not just navigating or validating information, but in using it to effectively influence the organization as a whole.  Knowledge is power in this environment.  Management took over the role of resource allocation from owners and focused on decision-making as the primary effort, using knowledge and the skills of middle management to inform those choices.

A symbol of knowledge productivity might be the meeting.  Meetings came to dominate the culture of organizations:  meetings to decide what to meet about, meetings to confirm that people were on the same page, meetings to follow-up from other meetings, and so on.  Management became very good at justifying meetings, the work that went into preparing, having, and following up from meetings.  Power derived from holding meetings, creating follow-up items and more.  The work products of meetings—the pre-reading memos, the presentations, the supporting analytics began to take on epic proportions.  Staff organizations developed that shadowed the whole process.

The essence of these meetings was to execute on a strategy—a multi-year commitment to create value, defend against competition, and to execute.  Much of the headquarters mindset of this era was devoted to strategic analysis and planning.

The very best companies became differentiated by their use of information technologies in now legendary ways such as to manage supply chain or deliver services to customers.  Companies like Wal-Mart pioneered the use of technology to bring lower prices and better inventory management.  Companies like the old MCI developed whole new products based entirely on the ability to write software to provide new ways of offering existing services.

Even with the broad availability of knowledge and information, companies still became trapped in the old ways of doing things, unable to adapt and change.  The role of disruption as a function not just of technology development but as management decision-making showed the intricate relationship between the two. With this era of information technology came the notion of companies too big and too slow to react to changes in the marketplace even with information right there in front of collective eyes.

The impact of software, as we finished the first decade of the 21st century, is more profound than even the most optimistic software people would have predicted.  As the entrepreneur and venture capitalist Marc Andreessen wrote two years ago, “software is eating the world”.  Software is no longer just about the internal workings of business or a way to analyze information and execute more efficiently, but has come to define what products a business develops, offers, and serves.  Software is now the product, from cars to planes to entertainment to banking and more. Every product not only has a major software component but it is also viewed and evaluated through the role of software.  Software is ultimately the product, or at least a substantial part of differentiation, for every product and service.

Today’s workplace: Continuous Productivity

Today’s workplace is as different as the office was from the factory.

Today’s organizations are either themselves mobile or serving customers that are mobile, or likely both.  Mobility is everywhere we look—from apps for consumers to sales people in stores and the cash registers to plane tickets.  With mobility comes an unprecedented degree of freedom and flexibility—freedom from locality, limited information, and the desktop computer.

The knowledge-based organization spent much energy on connecting the dots between qualitative sampling and data sourced on what could be measured. Much went into trying get more sources of data and to seek the exact right answer to important management decisions.  Today’s workplace has access to more data than ever before, but along with that came understanding that just because it came from a computer it isn’t right.  Data is telemetry based on usage from all aspects of the system and goes beyond sampling and surveys.  The use of data today substitutes algorithms seeking exact answers with heuristics informed by data guessing the best answer using a moment’s worth of statistical data.  Today’s answers change over time as more usage generates more data.  We no longer spend countless hours debating causality because what is happening is right there before our eyes.

We see this all the time in the promotion of goods on commerce sites, the use of keyword search and SEO, even the way that search itself corrects spellings or maps use a vast array of data to narrow a potentially very large set of results from queries.  Technologies like speech or vision have gone from trying to compute the exact answer to using real-time data to provide contextually relevant and even more accurate guesses.

The availability of these information sources is moving from a hierarchical access model of the past to a much more collaborative and sharing-first approach.  Every member of an organization should have access to the raw “feeds” that could be material to their role.  Teams become the focus of collaborative work, empowered by the data to inform their decisions.  We see the increasing use of “crowds” and product usage telemetry able to guide improved service and products, based not on qualitative sampling plus “judgment” but on what amounts to a census of real-world usage.

Information technology is at the heart of all of these changes, just as it was in the knowledge era.  The technologies are vastly different.  The mainframe was about centralized information and control.  The PC era empowered people to first take mainframe data and make better use of it and later to create new, but inherently local or workgroup specific information sources.  Today’s cloud-based services serve entire organizations easily and can also span the globe, organizations, and devices.  This is such a fundamental shift in the availability of information that it changes everything in how information is collected, shared, and put to use. It changes everything about the tools used to create, analyze, synthesize, and share information.

Management using yesterday’s techniques can’t seem keep up with this world. People are overwhelmed by the power of their customers with all this information (such as when social networks create a backlash about an important decision, or we visit a car dealer armed with local pricing information).  Within organizations, managers are constantly trying to stay ahead of the curve.  The “young” employees seem to know more about what is going on because of Twitter and Facebook or just being constantly connected.  Even information about the company is no longer the sole domain of management as the press are able to uncover or at least speculate about the workings of a company while employees see this speculation long before management is communicating with employees.  Where people used to sit in important meetings and listen to important people guess about information, people now get real data from real sources in real-time while the meeting is taking place or even before.

This symbol of the knowledge era, the meeting, is under pressure because of the inefficiency of a meeting when compared to learning and communicating via the technology tools of today.  Why wait for a meeting when everyone has the information required to move forward available on their smartphones?  Why put all that work into preparing a perfect pitch for a meeting when the data is changing and is a guess anyway, likely to be further informed as the work progresses?  Why slow down when competitors are speeding up?

There’s a new role for management that builds on this new level of information and employees skilled in using it.  Much like those who grew up with PC “natively” were quick to assume their usage in the workplace (some might remember the novelty of when managers first began to answer their own email), those who grow up with the socialplace are using it to do work, much to the chagrin of management.

Management must assume a new type of leadership that is focused on framing the outcome, the characteristics of decisions, and the culture of the organization and much less about specific decision-making or reviewing work.  The role of workplace technology has evolved significantly from theory to practice as a result of these tools. The following table contrasts the way we work between the historic norms and continuous productivity.

Then Now, Continuous Productivity
Process Exploration
Hierarchy, top down or middle out Network, bottom up
Internal committees Internal and external teams, crowds
Strategy-centric Execution-centric
Presenting packaged and produced ideas, documents Sharing ideas and perspectives continuously, service
Data based on snapshots at intervals, viewed statically Data always real-time, viewed dynamically
Process-centric Rhythm-centric
Exact answers Approximation and iteration
More users More usage

Today’s workplace technology, theory

Modern IT departments, fresh off the wave of PC standardization and broad homogenization of the IT infrastructure developed the tools and techniques to maintain, ne contain, the overall IT infrastructure.

A significant part of the effort involved managing the devices that access the network, primarily the PC.  Management efforts ran the gamut from logon scripts, drive scanning, anti-virus software, standard (or only) software load, imaging, two-factor authentication and more.  Motivating this has been the longstanding reliability and security problems of the connected laptop—the architecture’s openness so responsible for the rise of the device also created this fragility.  We can see this expressed in two symbols of the challenges faced by IT: the corporate firewall and collaboration.  Both of these technologies offer good theories but somewhat backfire in practice in today’s context.

With the rise of the Internet, the corporate firewall occupied a significant amount of IT effort.  It also came to symbolize the barrier between employees and information resources.  At some extremes, companies would routinely block known “time wasters” such as social networks and free email.  Then over time as the popularity of some services grew, the firewall would be selectively opened up for business purposes.  YouTube and other streaming services are examples of consumer services that transitioned to an approved part of enterprise infrastructure given the value of information available.  While many companies might view Twitter as a time-wasting service, the PR departments routinely use it to track news and customer service might use it to understand problems with products so it too becomes an expected part of infrastructure.  These “cracks” in the notion of enterprise v. consumer software started to appear.

Traditionally the meeting came to symbolize collaboration.  The business meeting which occupied so much of the knowledge era has taken on new proportions with the spread of today’s technologies.  Businesses have gone to great lengths to automate meetings and enhance them with services.  In theory this works well and enables remote work and virtual teams across locations to collaborate.  In practical use, for many users the implementation was burdensome and did not support the wide variety of devices or cross-organization scenarios required.  The merger of meetings with the traditional tools of meetings (slides, analysis, memos) was also cumbersome as sharing these across the spectrum of devices and tools was also awkward. We are all familiar with the first 10 minutes of every meeting now turning into a technology timesink where people get connected in a variety of ways and then sync up with the “old tools” of meetings while they use new tools in the background.

Today’s workspace technology, practice

In practice, the ideal view that IT worked to achieve has been rapidly circumvented by the low-friction, high availability of a wide variety of faster-to-use, easier-to-use, more flexible, and very low-cost tools that address problems in need of solutions.  Even though this is somewhat of a repeat of the introduction of PCs in the early 1990’s, this time around securing or locking down the usage of these services is far more challenging than preventing network access and isolating a device.  The Internet works to make this so, by definition.

Today’s organizations face an onslaught of personally acquired tablets and smartphones that are becoming, or already are, the preferred device for accessing information and communication tools.  As anyone who uses a smartphone knows, accessing your inbox from your phone quickly becomes the preferred way to deal with the bulk of email.  How often do people use their phones to quickly check mail even while in front of their PC (even if the PC is not in standby or powered off)?  How much faster is it to triage email on a phone than it is on your PC?

These personal devices are seen in airports, hotels, and business centers around the world.  The long battery life, fast startup time, maintenance-free (relatively), and of course the wide selection of new apps for a wide array of services make these very attractive.

There is an ongoing debate about “productivity” on tablets.  In nearly all ways this debate was never a debate, but just a matter of time.  While many look at existing scenarios to be replicated on a tablet as a measure of success of tablets at achieving “professional productivity”, another measure is how many professionals use their tablets for their jobs and leave their laptops at home or work.  By that measure, most are quick to admit that tablets (and smartphones) are a smashing success.  The idea that tablets are used only for web browsing and light email seems as quaint as claiming PCs cannot do the work of mainframes—a common refrain in the 1980s.  In practice, far too many laptops have become literally desktops or hometops.

While the use of tools such as AutoCAD, Creative Suite, or enterprise line of business tools will be required and require PCs for many years to come, the definition of professional productivity will come to include all the tasks that can be accomplished on smartphones and tablets.  The nature of work is changing and so the reality of the tools in use are changing as well.

Perhaps the most pervasive services for work use are cloud-based storage products such as DropBox, Hightail (YouSendIt), or Box.  These products are acquired easily by consumers, have straightforward browser-based interfaces and apps on all devices, and most importantly solve real problems required by modern information sharing.  The basic scenario of sharing large files with a customers or partners (or even fellow employees) across heterogeneous devices and networks is easily addressed by these tools.  As a result, expensive and elaborate (or often much richer) enterprise infrastructure goes unused for this most basic of business needs—sharing files.  Even the ubiquitous USB memory stick is used to get around the limitations of enterprise storage products, much to the chagrin of IT departments.

Tools beyond those approved for communication are routinely used by employees on their personal devices (except of course in regulated industries).  Tools such as WhatsApp or WeChat have hundreds of millions of users.  A quick look at Facebook or Twitter show that for many of those actively engaged the sharing of work information, especially news about products and companies, is a very real effort that goes beyond “the eggs I had for breakfast” as social networks have sometimes been characterized.  LinkedIn has become the goto place for sales people learning about customers and partners and recruiters seeking to hire (or headhunt) and is increasingly becoming a primary source of editorial content about work and the workplace.  Leading strategists are routinely read by hundreds of thousands of people on LinkedIn and their views shared among the networks employees maintain of their fellow employees.  It has become challenging for management to “compete” with the level and volume of discourse among employees.

The list of devices and services routinely used by workers at every level is endless.  The reality appears to be that for many employees the number of hours of usage in front of approved enterprise apps on managed enterprise devices is on the decline, unless new tablets and phones have been approved.  The consumerization of IT appears to be very real, just by anecdotally observing the devices in use on public transportation, airports, and hotels.  Certainly the conversation among people in suits over what to bring on trips is real and rapidly tilting towards “tablet for trips”, if not already there.

The frustration people have with IT to deliver or approve the use of services is readily apparent, just as the frustration IT has with people pushing to use insecure, unapproved, and hard to manage tools and devices.  Whenever IT puts in a barrier, it is just a big rock in the information river that is an organization and information just flows around it.  Forward-looking IT is working diligently to get ahead of this challenge, but the models used to reign in control of PCs and servers on corporate premises will prove of limited utility.

A new approach is needed to deal with this reality.

Transition versus disruption

The biggest risks organizations face is in thinking the transition to a new way of working will be just that, a transition, rather than a disruption.  While individuals within an organization, particularly those that might be in senior management, will seek to smoothly transition from one style of work to another, the bulk of employees will switch quickly. Interns, new hires, or employees looking for an edge see these changes as the new normal or the only normal they’ve ever experienced.  Our own experience with PCs is proof of how quickly change can take place.

In Only the Paranoid Survive, Andy Grove discussed breaking the news to employees of a new strategy at Intel only to find out that employees had long ago concluded the need for change—much to the surprise of management.  The nature of a disruptive change in management is one in which management believes they are planning a smooth transition to new methods or technologies only to find out employees have already adopted them.

Today’s technology landscape is one undergoing a disruptive change in the enterprise—the shift to cloud based services, social interaction, and mobility.  There is no smooth transition that will take place.  Businesses that believe people will gradually move from yesterday’s modalities of work to these new ways will be surprised to learn that people are already working in these new ways. Technologists seeking solutions that “combine the best of both worlds” or “technology bridge” solutions will only find themselves comfortably dipping their toe in the water further solidifying an old approach while competitors race past them.  The nature of disruptive technologies is the relentless all or nothing that they impose as they charge forward.

While some might believe that continuing to focus on “the desktop” will enable a smoother transition to mobile (or consumer) while the rough edges are worked out or capabilities catch up to what we already have, this is precisely the innovator’s dilemma – hunkering down and hoping things will not take place as quickly as they seem to be for some.  In fact, to solidify this point of view many will point to a lack of precipitous decline or the mission critical nature in traditional ways of working.  The tail is very long, but innovation and competitive edge will not come from the tail.  Too much focus on the tail will risk being left behind or at the very least distract from where things are rapidly heading. Compatibility with existing systems has significant value, but is unlikely to bring about more competitive offerings, better products, or step-function improvements in execution.

Culture of continuous productivity

The culture of continuous productivity enabled by new tools is literally a rewrite of the past 30 years of management doctrine.  Hierarchy, top-down decision making, strategic plans, static competitors, single-sided markets, and more are almost quaint views in a world literally flattened by the presence of connectivity, mobility, and data. The impact of continuous productivity can be viewed through the organization, individuals and teams, and the role of data.

The social and mobile aspects of work, finally, gain support of digital tools and with those tools the realization of just how much of nearly all work processes are intrinsically social.   The existence and paramount importance of “document creation tools” as the nature of work appear, in hindsight, to have served as a slight detour of our collective focus.  Tools can now work more like we like to work, rather than forcing us to structure our work to suit the tools.  Every new generation of tools comes with promises of improvements, but we’ve already seen how the newest styles of work lead to improvements in our lives outside of work. Where it used to be novel for the person with a PC to use those tools to organize a sports team or school function, now we see the reverse and we see the tools for the rest of life being used to improve our work.

This existence proof makes this revolution different.  We already experience the dramatic improvements in our social and non-work “processes”.  With the support and adoption of new tools, just as our non-work lives saw improvements we will see improvements in work.

The cultural changes encouraged or enabled by continuous productivity include:

  • Innovate more and faster.  The bottom line is that by compressing the time between meaningful interactions between members of a team, we will go from problem to solution faster.  Whether solving a problem with an existing product or service or thinking up a new one, the continuous nature of communication speeds up the velocity and quality of work. We all experience the pace at which changes outside work take place compared to the slow pace of change within our workplaces.
  • Flatten hierarchy. The difficulty in broad communication, the formality of digital tools, and restrictions on the flow of information all fit perfectly with a strict hierarchical model of teams.  Managers “knew” more than others.  Information flowed down.  Management informed employees.  Equal access to tools and information, a continuous multi-way dialog, and the ease and bringing together relevant parties regardless of place in the organization flattens the hierarchy.  But more than that, it shines a light on the ineffectiveness and irrelevancy of a hierarchy as a command structure.

  • Improve execution.  Execution improves because members of teams have access to the interactions and data in real-time.  Gone are the days of “game of telephone” where information needed to “cascade” through an organization only to be reinterpreted or even filtered by each level of an organization.
  • Respond to changes using telemetry / data.  With the advent of continuous real-world usage telemetry, the debate and dialog move from deciding what the problems to be solved might be to solving the problem.  You don’t spend energy arguing over the problem, but debating the merits of various solutions.

  • Strengthen organization and partnerships.  Organizations that communicate openly and transparently leave much less room for politics and hidden agendas.  The transparency afforded by tools might introduce some rough and tumble in the early days as new “norms” are created but over time the ability to collaborate will only improve given the shared context and information base everyone works from.
  • Focus on the destination, not the journey.  The real-time sharing of information forces organizations to operate in real-time. Problems are in the here and now and demand solutions in the present. The benefit of this “pressure” is that a focus on the internal systems, the steps along the way, or intermediate results is, out of necessity, de-emphasized.

Organization culture change

Continuously productive organizations look and feel different from traditional organizations. As a comparison, consider how different a reunion (college, family, etc.) is in the era of Facebook usage. When everyone gets together there is so much more that is known—the reunion starts from shared context and “intimacy”.  Organizations should be just as effective, no matter how big or how geographically dispersed.

Effective organizations were previously defined by rhythms of weekly, monthly and quarterly updates.  These “episodic” connection points had high production values (and costs) and ironically relatively low retention and usage.  Management liked this approach as it placed a high value on and required active management as distinct from the work.  Tools were designed to run these meetings or email blasts, but over time these were far too often over-produced and tended to be used more for backward looking pseudo-accountability.

Looking ahead, continuously productive organizations will be characterized by the following:

  • Execution-centric focus.  Rather than indexing on the process of getting work done, the focus will shift dramatically to execution. The management doctrine of the late 20th century was about strategy.  For decades we all knew that strategy took a short time to craft in reality, but in practice almost took on a life of its own. This often led to an ever-widening gap between strategy and execution, with execution being left to those of less seniority.  When everyone has the ability to know what can be known (which isn’t everything) and to know what needs to be done, execution reigns supreme.  The opportunity to improve or invent will be everywhere and even with finite resources available, the biggest failure of an organization will be a failure to act.
  • Management framing context with teams deciding. Because information required discovery and flowed (deliberately) inefficiently management tasked itself with deciding “things”. The entire process of meetings degenerated into a ritualized process to inform management to decide amongst options while outside the meeting “everyone” always seemed to know what to do. The new role of management is to provide decision-making frameworks, not decisions.  Decisions need to be made where there is the most information. Framing the problem to be solved out of the myriad of problems and communicating that efficiently is the new role of management.
  • Outside is your friend.  Previously the prevailing view was that inside companies there was more information than there was outside and often the outside was viewed as being poorly informed or incomplete. The debate over just how much wisdom resides in the crowd will continue and certainly what distinguishes companies with competitive products will be just how they navigate the crowd and simultaneously serve both articulated and unarticulated needs.  For certain, the idea that the outside is an asset to the creation of value, not just the destination of value, is enabled by the tools and continuous flow of information.
  • Employees see management participate and learn, everyone has the tools of management.  It took practically 10 years from the introduction of the PC until management embraced it as a tool for everyday use by management.  The revolution of social tools is totally different because today management already uses the socialplace tools outside of work. Using Twitter for work is little different from using Facebook for family.  Employees expect management to participate directly and personally, whether the tool is a public cloud service or a private/controlled service. The idea of having an assistant participate on behalf of a manager with a social tool is as archaic as printing out email and typing in handwritten replies. Management no longer has separate tools or a different (more complete) set of books for the business, but rather information about projects and teams becomes readily accessible.
  • Individuals own devices, organizations develop and manage IP. PCs were first acquired by individual tech enthusiasts or leading edge managers and then later by organizations.  Over time PCs became physical assets of organizations.  As organizations focused more on locking down and managing those assets and as individuals more broadly had their own PCs, there was a decided shift to being able to just “use a computer” when needed.  The ubiquity of mobile devices almost from the arrival of smartphones and certainly tablets, has placed these devices squarely in the hands of individuals. The tablet is mine. And because it is so convenient for the rest of my life and I value doing a good job at work, I’m more than happy to do work on it “for free”.  In exchange, organizations are rapidly moving to tools and processes that more clearly identify the work products as organization IP not the devices.  Cloud-based services become the repositories of IP and devices access that through managed credentials.

Individuals and teams work differently

The new tools and techniques come together to improve upon the way individuals and teams interact.  Just as the first communication tools transformed business, the tools of mobile and continuous productivity change the way interactions happen between individuals and teams.

  • Sense and respond.  Organizations through the PC era were focused on planning and reacting cycles.  The long lead time to plan combined with the time to plan a reaction to events that were often delayed measurements themselves characterized “normal”.  New tools are much more real-time and the information presented represents the whole of the information at work, not just samples and surveys.  The way people will work will focus much more on everyone being sensors for what is going on and responding in real-time.  Think of the difference between calling for a car or hailing a cab and using Uber or Lyft from either a consumer perspective or from the business perspective of load balancing cars and awareness of the assets at hand as representative to sensing and responding rather than planning.
  • Bottom up and network centric.  The idea of management hierarchy or middle management as gatekeepers is being broken down by the presence of information and connectivity.  The modern organization working to be the most productive will foster an environment of bottom up—that is people closest to the work are empowered with information and tools to respond to changes in the environment.  These “bottoms” of the organization will be highly networked with each other and connected to customers, partners, and even competitors.  The “bandwidth” of this network is seemingly instant, facilitated by information sharing tools.
  • Team and crowd spanning the internal and external.  The barriers of an organization will take on less and less meaning when it comes to the networks created by employees.  Nearly all businesses at scale are highly virtualized across vendors, partners, and customers.  Collaboration on product development, product implementation, and product support take place spanning information networks as well as human networks.  The “crowd” is no longer a mob characterized by comments on a blog post or web site, but can be structured and systematically tapped with rich demographic information to inform decisions and choices.
  • Unstructured work rhythm.  The highly structured approach to work that characterized the 20th century was created out of a necessity for gathering, analyzing, and presenting information for “costly” gatherings of time constrained people and expensive computing.  With the pace of business and product change enabled by software, there is far less structure required in the overall work process.  The rhythm of work is much more like routine social interactions and much less like daily, weekly, monthly staff meetings.  Industries like news gathering have seen these radical transformations, as one example.

Data becomes pervasive (and big)

With software capabilities come ever-increasing data and information.  While the 20th century enabled the collection of data and to a large degree the analysis of data to yield ever improving decisions in business, the prevalence of continuous data again transforms business.

  • Sharing data continuously.  First and foremost, data will now be shared continuously and broadly within organizations. The days when reports were something for management and management waited until the end of the week or month to disseminate filtered information are over.  Even though financial data has been relatively available, we’re now able to see how products are used, trouble shoot problems customers might be having, understand the impact of small changes, and try out alternative approaches.  Modern organizations will provide tools that enable the continuous sharing of data through mobile-first apps that don’t require connectivity to corporate networks or systems chained to desktop resources
  • Always up to date.  The implication of continuously sharing information means that everyone is always up to date.  When having a discussion or meeting, the real world numbers can be pulled up right then and there in the hallway or meeting room.  Members of teams don’t spend time figuring out if they agree on numbers, where they came from or when they were “pulled”.  Rather the tools define the numbers people are looking at and the data in those tools is the one true set of facts.
  • Yielding best statistical approach informed by telemetry (induction).  The notion that there is a “right” answer is antiquated as the printed report.  We can now all admit that going to a meeting with a printed out copy of “the numbers” is not worth the debate over the validity or timeframe of those numbers (“the meeting was rescheduled, now we have to reprint the slides.”)  Meetings now are informed by live data using tools such as Mixpanel or live reporting from Workday, Salesforce and others.  We all know now that “right” is the enemy of “close enough” given that the datasets we can work with are truly based on census and not surveys.  This telemetry facilitates an inductive approach to decision-making.
  • Valuing more usage.  Because of the ability to truly understand the usage of products—movies watched, bank accounts used, limousines taken, rooms booked, products browsed and more—the value of having more people using products and services increases dramatically.  Share matters more in this world because with share comes the best understanding of potential growth areas and opportunities to develop for new scenarios and new business approaches.

New generation of productivity tools, examples and checklist

Bringing together new technologies and new methods for management has implications that go beyond the obvious and immediate.  We will all certainly be bringing our own devices to work, accessing and contributing to work from a variety of platforms, and seeing our work take place across organization boundaries with greater ease.  We can look very specifically at how things will change across the tools we use, the way we communicate, how success is measured, and the structure of teams.

Tools will be quite different from those that grew up through the desktop PC era.  At the highest level the implications about how tools are used are profound.  New tools are being developed today—these are not “ports” of existing tools for mobile platforms, but ideas for new interpretations of tools or new combinations of technologies.  In the classic definition of innovator’s dilemma, these new tools are less functional than the current state-of-the-art desktop tools.  These new tools have features and capabilities that are either unavailable or suboptimal at an architectural level in today’s ubiquitous tools.  It will be some time, if ever, before new tools have all the capabilities of existing tools.  By now, this pattern of disruptive technologies is familiar (for example, digital cameras, online reading, online videos, digital music, etc.).

The user experience of this new generation of productivity tools takes on a number of attributes that contrast with existing tools, including:

  • Continuous v. episodic. Historically work took place in peaks and valleys.  Rough drafts created, then circulated, then distributed after much fanfare (and often watering down).  The inability to stay in contact led to a rhythm that was based on high-cost meetings taking place at infrequent times, often requiring significant devotion of time to catching up. Continuously productive tools keep teams connected through the whole process of creation and sharing.  This is not just the use of adjunct tools like email (and endless attachments) or change tracking used by a small number of specialists, but deep and instant collaboration, real-time editing, and a view that information is never perfect or done being assembled.
  • Online and shared information.  The old world of creating information was based on deliberate sharing at points in time.  Heavyweight sharing of attachments led to a world where each of us became “merge points” for work. We worked independently in silos hoping not to step on each other never sure where the true document of record might be or even who had permission to see a document.  New tools are online all the time and by default.  By default information can be shared and everyone is up to date all the time.
  • Capture and continue  The episodic nature of work products along with the general pace of organizations created an environment where the “final” output carried with it significant meaning (to some).  Yet how often do meetings take place where the presenter apologizes for data that is out of date relative to the image of a spreadsheet or org chart embedded in a presentation or memo?  Working continuously means capturing information quickly and in real-time then moving on.  There are very few end points or final documents.  Working with customers and partners is a continuous process and the information is continuous as well.
  • Low startup costs.  Implementing a new system used to be a time consuming and elaborate process viewed as a multi-year investment and deployment project.  Tools came to define the work process and more critically make it impossibly difficult to change the work process.  New tools are experienced the same way we experience everything on the Internet—we visit a site or download an app and give it a try.  The cost to starting up is a low-cost subscription or even a trial.  Over time more features can be purchased (more controls, more depth), but the key is the very low-cost to begin to try out a new way to work.  Work needs change as market dynamics change and the era of tools preventing change is over.
  • Sharing inside and outside.  We are all familiar with the challenges of sharing information beyond corporate boundaries.  Management and IT are, rightfully, protective of assets.  Individuals struggle with the basics of getting files through firewalls and email guards.  The results are solutions today that few are happy with.  Tools are rapidly evolving to use real identities to enable sharing when needed and cross-organization connections as desired.  Failing to adopt these approaches, IT will be left watching assets leak out and workarounds continue unabated.
  • Measured enterprise integration.  The PC era came to be defined at first by empowerment as leading edge technology adopters brought PCs to the workplace.  The mayhem this created was then controlled by IT that became responsible to keep PCs running, information and networks secure, and enforce consistency in organizations for the sake of sharing and collaboration.  Many might (perhaps wrongly) conclude that the consumerization wave defined here means IT has no role in these tasks.  Rather the new era is defined by a measured approach to IT control and integration.  Tools for identity and device management will come to define how IT integrates and controls—customization or picking and choosing code are neither likely nor scalable across the plethora of devices and platforms that will be used by people to participate in work processes. The net is to control enterprise information flow, not enterprise information endpoints.
  • Mobile first.  An example of a transition between the old and new, many see the ability to view email attachments on mobile devices as a way forward.  However, new tools imply this is a true bridge solution as mobility will come to trump most everything for a broad set of people.  Deep design for architects, spreadsheets for analysts, or computation for engineers are examples that will likely be stationary or at least require unique computing capabilities for some time. We will all likely be surprised by the pace at which even these “power” scenarios transition in part to mobile.  The value of being able to make progress while close to the site, the client, or the problem will become a huge asset for those that approach their professions that way.
  • Devices in many sizes. Until there is a radical transformation of user-machine interaction (input, display), it is likely almost all of us will continue to routinely use devices of several sizes and those sizes will tend to gravitate towards different scenarios (see http://blog.flurry.com/bid/99859/The-Who-What-and-When-of-iPhone-and-iPad-Usage), though commonality in the platforms will allow for overlap.  This overlap will continue to be debated as “compromise” by some.  It is certain we will all have a device that we carry and use almost all the time, the “phone”.  A larger screen device will continue to better serve many scenarios or just provide a larger screen area upon which to operate.  Some will find a small tablet size meeting their needs almost all of the time.  Others will prefer a larger tablet, perhaps with a keyboard.  It is likely we will see somewhat larger tablets arise as people look to use modern operating systems as full-time replacements for existing computing devices.  The implications are that tools will be designed for different device sizes and input modalities.

It is worth considering a few examples of these tools.  As an illustration, the following lists tools in a few generalized categories of work processes.  New tools are appearing almost every week as the opportunity for innovation in the productivity space is at a unique inflection point.  These examples are just a few tools that I’ve personally had a chance to experience—I suspect (and hope) that many will want to expand these categories and suggest additional tools (or use this as a springboard for a dialog!)

The architecture and implementation of continuous productivity tools will also be quite different from the architecture of existing tools.  This starts by targeting a new generation of platforms, sealed-case platforms.

The PC era was defined by a level of openness in architecture that created the opportunity for innovation and creativity that led to the amazing revolution we all benefit from today.  An unintended side-effect of that openness was the inherent unreliability over time, security challenges, and general futzing that have come to define the experience many lament.  The new generation of sealed case platforms—that is hardware, software, and services that have different points of openness, relative to previous norms in computing, provide for an experience that is more reliable over time, more secure and predictable, and less time-consuming to own and use.  The tradeoff seems dramatic (or draconian) to those versed in old platforms where tweaking and customizing came to dominate.  In practice the movement up the stack, so to speak, of the platform will free up enormous amounts of IT budget and resources to allow a much broader focus on the business.  In addition, choice, flexibility, simplicity in use, and ease of using multiple devices, along with a relative lack of futzing will come to define this new computing experience for individuals.

The sealed case platforms include iOS, Android, Chromebooks, Windows RT, and others.  These platforms are defined by characteristics such as minimizing APIs that manipulate the OS itself, APIs that enforce lower power utilization (defined background execution), cross-application security (sandboxing), relative assurances that apps do what they say they will do (permissions, App Stores), defined semantics for exchanging data between applications, and enforced access to both user data and app state data.  These platforms are all relatively new and the “rules” for just how sealed a platform might be and how this level of control will evolve are still being written by vendors.  In addition, devices themselves demonstrate the ideals of sealed case by restricting the attachment of peripherals and reducing the reliance on kernel mode software written outside the OS itself.  For many this evolution is as controversial as the transition automobiles made from “user-serviceable” to electronic controlled engines, but the benefits to the humans using the devices are clear.

Building on the sealed case platform, a new generation of applications will exhibit a significant number of the following attributes at the architecture and implementation level.  As with all transitions, debates will rage over the relative strength or priority of one or more attributes for an app or scenario (“is something truly cloud” or historically “is this a native GUI”).  Over time, if history is any guide, the preferred tools will exhibit these and other attributes as a first or native priority, and de-prioritize the checklists that characterized the “best of” apps for the previous era.

The following is a checklist of attributes of tools for continuous productivity:

  • Mobile first. Information will be accessed and actions will be performed mobile first for a vast majority of both employees and customers.  Mobile first is about native apps, which is likely to create a set of choices for developers as they balance different platforms and different form factors.
  • Cloud first.  Information we create will be stored first in the cloud, and when needed (or possible) will sync back to devices.  The days of all of us focusing on the tasks of file management and thinking about physical storage have been replaced by essentially unlimited cloud storage.  With cloud-storage comes multi-device access and instant collaboration that spans networks.  Search becomes an integral part of the user-experience along with labels and meta-data, rather than physical hierarchy presenting only a single dimension.  Export to broadly used interchange formats and printing remain as critical and archival steps, but not the primary way we share and collaborate.
  • User experience is platform native or browser exploitive.  Supporting mobile apps is a decision to fully use and integrate with a mobile platform.  While using a browser can and will be a choice for some, even then it will become increasingly important to exploit the features unique to a browser.  In all cases, the usage within a customer’s chosen environment encourages the full range of support for that platform environment.
  • Service is the product, product is the service.  Whether an internal IT or a consumer facing offering, there is no distinction where a product ends and a continuously operated and improving service begins.  This means that the operational view of a product is of paramount importance to the product itself and it means that almost every physical product can be improved by a software service element.
  • Tools are discrete, loosely coupled, limited surface area.  The tools used will span platforms and form factors.  When used this way, monolithic tools that require complex interactions will fall out of favor relative to tools more focused in their functionality.  Doing a smaller set of things with focus and alacrity will provide more utility, especially when these tools can be easily connected through standard data types or intermediate services such as sharing, storage, and identity.
  • Data contributed is data extractable.  Data that you add to a service as an end-user is easily extracted for further use and sharing.  A corollary to this is that data will be used more if it can also be extracted a shared.  Putting barriers in place to share data will drive the usage of the data (and tool) lower.
  • Metadata is as important as data.  In mobile scenarios the need to search and isolate information with a smaller user interface surface area and fewer “keystrokes” means that tools for organization become even more important.  The use of metadata implicit in the data, from location to author to extracted information from a directory of people will become increasingly important to mobile usage scenarios.
  • Files move from something you manage to something you use when needed.  Files (and by corollary mailboxes) will simply become tools and not obsessions.  We’re all seeing the advances in unlimited storage along with accurate search change the way we use mailboxes.  The same will happen with files.  In addition, the isolation and contract-based sharing that defines sealed platforms will alter the semantic level at which we deal with information.  The days of spending countless hours creating and managing hierarchies and physical storage structures are over—unlimited storage, device replication, and search make for far better alternatives.  
  • Identity is a choice.  Use of services, particularly consumer facing services, requires flexibility in identity.  Being able to use company credentials and/or company sign-on should be a choice but not a requirement.  This is especially true when considering use of tools that enable cross-organization collaboration. Inviting people to participate in the process should be as simple as sending them mail today.
  • User experience has a memory and is aware and predictive.  People expect their interactions with services to be smart—to remember choices, learn preferences, and predict what comes next.  As an example, location-based services are not restricted to just maps or specific services, but broadly to all mobile interactions where the value of location can improve the overall experience.
  • Telemetry is essential / privacy redefined.  Usage is what drives incremental product improvements along with the ability to deliver a continuously improving product/service.  This usage will be measured by anonymous, private, opt-in telemetry.  In addition, all of our experiences will improve because the experience will be tailored to our usage.  This implies a new level of trust with regard to the vendors we all use.  Privacy will no doubt undergo (or already has undergone) definitional changes as we become either comfortable or informed with respect to the opportunities for better products.   
  • Participation is a feature.  Nearly every service benefits from participation by those relevant to the work at hand.  New tools will not just enable, but encourage collaboration and communication in real-time and connected to the work products.  Working in one place (document editor) and participating in another (email inbox) has generally been suboptimal and now we have alternatives.  Participation is a feature of creating a work product and ideally seamless.
  • Business communication becomes indistinguishable from social.  The history of business communication having a distinct protocol from social goes back at least to learning the difference between a business letter and a friendly letter in typing class.  Today we use casual tools like SMS for business communication and while we will certainly be more respectful and clear with customers, clients, and superiors, the reality is the immediacy of tools that enable continuous productivity will also create a new set of norms for business communication.  We will also see the ability to do business communication from any device at any time and social/personal communication on that same device drive a convergence of communication styles.
  • Enterprise usage and control does not make things worse. In order for enterprises to manage and protect the intellectual property that defines the enterprise and the contribution employees make to the enterprise IP, data will need to be managed.  This is distinctly different from managing tools—the days of trying to prevent or manage information leaks by controlling the tools themselves are likely behind us.  People have too many choices and will simply choose tools (often against policy and budgets) that provide for frictionless work with coworkers, partners, customers, and vendors.  The new generation of tools will enable the protection and management of information that does not make using tools worse or cause people to seek available alternatives.  The best tools will seamlessly integrate with enterprise identity while maintaining the consumerization attributes we all love.

What comes next?

Over the coming months and years, debates will continue over whether or not the new platforms and newly created tools will replace, augment, or see occasional use relative to the tools with which we are all familiar.  Changes as significant as those we are experiencing right now happen two ways, at first gradually and then quickly, to paraphrase Hemingway. Some might find little need or incentive to change. Others have already embraced the changes.  Perhaps those right now on the cusp, realize that the benefits of their new device and new apps are gradually taking over their most important work and information needs.  All of these will happen.  This makes for a healthy dialog.

It also makes for an amazing opportunity to transform how organizations make products, serve customers, and do the work of corporations.  We’re on the verge of seeing an entire rewrite of the management canon of the 20th century.  New ways of organizing, managing, working, collaborating are being enabled by the tools of the continuous productivity paradigm shift.

Above all, it makes for an incredible opportunity for developers and those creating new products and services.  We will all benefit from the innovations in technology that we will experience much sooner than we think.

–Steven Sinofsky

Written by Steven Sinofsky

August 20, 2013 at 7:00 am

Delegating or micromanaging, threading the needle

with 15 comments

delegationMicromanagement can be a reflection of a manager’s feedback and concerns about progress.  Empowerment can create a detached or worried manager.  Threading the needle between delegation and micromanagement is central to the relationship between a manager and a report.  How do you balance this as either a manager or employee?

Be sure to check out the poll results at the end of this post on the topic of why meetings are so ineffective.  This week’s poll is https://www.surveymonkey.com/s/NTSCCCK

A first year MBA student made the following observation:

High-performing people generally want autonomy to get things done without anyone micromanaging them.  At the same time, as a midlevel manager, I’ve often had someone above me who’s holding me accountable for whatever my direct reports are working on.

I’m struggling to find the right balance between giving people their autonomy while also asking sufficient questions to get the detail I need in order to feel comfortable with how things are going. 

This situation is not uncommon and represents a most fundamental challenge in any management hierarchy.  The situation boils down to a manager feeling accountable, employees wanting the freedom to do the work the best way they know how, and those outside this context assuming all is functioning well.

Here are 5 suggestions for improving the delegation process and avoiding the label of micromanagement:

  • Delegate the problem, don’t solve it.  The first sign of micromanaging is when delegating a project you also delegate the specifics of the solution.  While that makes sense in some fields, in creative or information work, being told up front the steps to follow makes one feel like a vendor and not a partner in the work.  This type of delegation doesn’t have the feeling that it enhances skills or career.  If the steps are well-known then perhaps there is a different view of the problem or delegation that will better suit a creative member of the team.
  • Share experiences, don’t instruct.  As the work progresses there’s a chance that the manager will see a pattern or similar situation arise.  There’s a good chance the way that experience is communicated can come across as either “sage sharing of experiences” or “more micromanaging”.  If there are experiences to share then share the story and allow the learning to take place by allegory and not turn the learning into “just do these steps”.
  • Listen to progress, don’t review it.  Just as managers should be delegating the problem, not the steps to solving it, when it comes time for progress to be reported it is best to let folks report on the progress the way it works best.  Micromanaging can also take the form of being specific about how progress should be reported or “summoning” people to review the progress.  If folks have been asked to take on a project, make sure they have the freedom to define the mechanics of the project as well.
  • Provide feedback, don’t course correct.  Things might not be always going as well as everyone wants and when that happens managers can sometimes slip into “gotta get this fixed” mode.  This type of course correction can remove many of the downstream benefits of delegation and turn into a big negative for folks.  It not only disempowers, but demotivates.  When things aren’t going well, the time is right for honest feedback and a two-way dialog.
  • Communicate serendipitously, don’t impede progress.  All projects have more work and less time than they need.  One way to reduce the amount of time available to make forward progress is for management to call for reviews or updates in a formal manner (meetings, written reports).  This type of communication can slow things down—the preparation, the review, the general stand-down while these work products are created.  If management is concerned about how things are going, then make it a point of finding the balance between serendipitous contact with the team and bugging them too much.

Above all, treat folks as you would like to be treated and validate that approach.  If you are the type of person that is eager to request and receive feedback then chances are you won’t see an eager manager as micromanaging you.  But if you are the type of person that likes some elbow room and your manager is the eager provider of feedback, then that mismatch is likely to be perceived as micromanagement rather than empowering delegation.

The simple solution to this potential dilemma is to communicate about these stylistic expectations before the work really starts.  Even if you’ve worked together for a while and have a rhythm, a new project might come with new approaches for working together.

Delegation can take the form of management asking for work from the team or it can take the form of “we’re all in this together”.  The question to ask yourself is if you delegate work so you’re part of “us” or “them”?

What are some tools you use for effective delegation?  Check out the poll – https://www.surveymonkey.com/s/NTSCCCK.

–Steven Sinofsky

 

Thanks for everyone that responded to our survey for “Using meetings to be more effective”.  In this survey, we hoped to learn together about the tools and characteristics that make meeting successful.

Here are the results:

  • About half of our most recent meetings include a phone bridge, with about one third connecting via Voice over IP (i.e. Skype)
  • In about one in six meetings, at least one person joins via a cell phone
  • About half of our meetings take advantage of screen sharing and about half involve PowerPoint, though only in about one third was a projector used
  • When asked about whether our last meeting was a success, on average (mean and median) we “neither agree nor disagree” that it was a success

In looking at drivers for what made us rate a meeting a success, there were some interesting findings:

  • Regarding technologies, of the technologies queried (phone, cell, VoIP, screen sharing, PowerPoint, projector, and meeting software), only the use of a projector had a statistically significant impact on our success rating.  However, meetings with a projector ranked half a point lower on a five point scale, than those without projectors
  • Interestingly, presenters rated meetings with projectors lower than members of the audience, with a difference of about a half point, it’s worth noting this was not correlated with slideshow software like PowerPoint
  • Of the tips for success discussed,  “a fully understood context” drove the success factor up a third-point , and  a “concise” meeting (brevity) drove success up nearly a half-point.
  • Interestingly, presenters rated meetings with “a fully understood context” higher than members of the audience

Bottom Line:

Modern meetings leverage online tools like to get everyone on the same page, though care should be taken during in-person meetings to not let the audio/visuals detract from your message as a presenter.  Taking time before and during the meeting to create a shared sense of context and keeping your message concise seem to drive the best outcomes for everyone, presenter and audience alike.

Thanks, Cameron

# # # # #

Written by Steven Sinofsky

June 18, 2013 at 9:30 am

Posted in posts

Tagged with , ,

Being a leader, not a micromanaging editor: 3 patterns to avoid

with 14 comments

12 O'Clock HighAs a manager, big company or small, the opportunities to lead are everywhere. Too often though we can fail to lead and fall into the trap of editing the work of others–critiquing, tweaking, or otherwise mucking with what is discussed or delivered, rather than stepping back and considering if we are truly improving on the work or just imprinting upon the work, or if we are empowering or micromanaging.

Please don’t forget to try the new poll for this post here.

Every manager faces a constant struggle as the work expands and time shrinks—it seems faster to just say “the answer” rather than let “discovery” happen organically. Finding this balance and challenging ourselves to lead not edit is difficult but key to the long term strength of the team and ability to scale as a manager.

The challenge gets to the core responsibilities of management. Management, at every level, is about the effort to frame challenges, define end states, and allocate resources to navigate between them. If the work requires smart, talented, creative people, then more than anything you want to enable folks on the team to create. When people create, they want to show off their creation and keep creating more. Redoing, reworking, and revisiting can not only drain resources and energy, but sap creative people of their desire to create.

Micromanaging by editing

Most would probably agree that the easiest and most damming insult directed at a manager is the dreaded label micromanager.

Looking beyond the rhetoric, the term editor does more to explain the dynamic. Editing the work of those you manage disempowers the team, removes accountability, and in general reduces motivation. Editing the work of others is easy—it seems like anyone can change the UX, add a feature, rewrite some text, or tweak a slide. The creative effort is coming up with the work in the first place from a blank sheet, so to speak. Of course there is a role for editing (which itself is a noble profession), but in the complex works of product development there is a great deal of context. In reality most everything follows an iceberg principle, with far more than meets the eye—the complexities and realities that came to light during creation might not always be visible once the work is packaged up for management.

For a variety of reasons theorized in this Wikipedia entry on micromanagement, managers might resort to an excessive focus on details or dive into details arbitrarily. A common element is the manager taking the work of a team member as a starting point and substituting a flawed process of editing for what could be helpful, insightful, and valued interactions more defined by proper feedback or coaching.

From the perspective of the manager, there are a number of common patterns that arise and are indicative of management needing improvement.

  1. Receive and rework. You glance at your mobile and that updated specification shows up. While there is an expectation to read the spec and provide feedback, the sender was probably hoping for a job well done reply. Instead, your message back is a quick “did you think of X” or “I don’t like the way you say Y”. This gets even worse if the feedback is about the presentation of the information rather than the information. You hope to be improving the work but inadvertently spin up a PowerPoint or Excel workshop session. There might very well be mistakes or significant missteps in the work. Step back and deliver a clear and focused message on those and just skip the easy adds or tweaks. Suggestion: Make a simple rule for yourself like “never suggest a different format of a report” or “never add more work unless you also take away work” or “save feedback for the critical or strategic elements”.
  2. Delegate and tweak. When you delegate work to the member of the team, your job is to clearly frame success and describe the objectives. Delegation of work can be as simple as scrubbing the feature list or as complex as asking someone to take on a group-wide stretch assignment. No matter what the scale of delegation, getting out of the way after delegation is key. When the results are in, keep in mind not the results free of context but look at the results in the context of how you delegated the work. If you see mistakes or missteps, ask yourself if you were clear or your delegation caused the problems. Editing the work that ignores the context will tend to alienate folks as they keep thinking “would have been nice if you told me that up front”. Leading is actively taking responsibility for the lack of clarity and triaging the real marginal gain from tweaks at this later stage. Suggestion: Delegate challenges and define success, but don’t delegate the intermediate steps or detailed output, making it clear where creativity is expected.
  3. Fetch and edit. The best work for creative folks on the team is when the problem is big and the solution escapes everyone. In these cases, as a manager you don’t know the answer. That’s stressful for everyone. The way to increase the stress is to ask a member of the team to build or create an answer for “review” or for a list of options and recommendations. We all know how this process can really go haywire. When one potential solution to an unknown is offered, the next step is to go back and rework it with the new learning, or “no not that rock, a different rock”. We also know that with a big unknown and a list of n possible choices, after a brief dialog the next step is to pick option n+1. Suggestion: Asking creative people solve vaguely defined problems can be the most rewarding work of the team, so don’t drain the energy by thinking you will know the best answer when you see it, driving folks a bit loopy in the process.

Leadership is more than editing

These patterns and others all share a common result—the more you do them, the less creative and engaged your team will be over time. Each time your employ the tools of editor, rather than leader, you encourage people to stop creating and focus their energies on trying to predict your editorial reaction.

Leading is contributing data and experience–share your related experience and let the allegory and discovery do the work.

Leading is coaching–share your observations and offer pros and cons.

Leading is walking through the action/reaction decision tree—share the path, not just the destination.

Leading is reiterating accountability in so many cases.

Leading is knowing when the potential for learning and growing outweigh the risk of failure.

Leading is realizing there a few perfect answers and many great answers.

A goal of leading is to amplify your skills and experience while also growing new leaders. If you’re not giving people room to uncover their own way and ultimately solutions, then you’re creating a staff organization for you, not the next generation of leaders. As valuable as your experience is, don’t forget that the minutes or hour you spend editing compare to days and weeks often spent getting the work into a consumable format. The bigger the investment the more expert people are, even if they would benefit from coaching and experience.

Over time as you work to keep focused on leadership rather than editing, the team grows stronger and more self-reliant. Members of the team worry more about getting the best answers and work and less about wondering what management might be after. More work gets done. Members of the team are more empowered. This positive feedback loop continues to improve every aspect of the team.

–Steven

Three questions – insights from readers

In the post, Combining guessing and planning in product development, our resident big data researcher at Stanford proposed a few questions in order to reflect what those reading this blog have to say. Considering the overall clicks on posts, we’re seeing about 1-2% of readers participate in this “for entertainment purpose only” poll.

The poll on this new post can be found https://www.surveymonkey.com/s/VLHQSBJ, please participate and share your perspective.

Thanks to those of you that took a minute to answer our three questions. We saw a few noteworthy points from the results:

  • Roughly half of you have had skip level meetings in the last six months.
  • On average, you spend about one fifth of your project schedule planning.
  • Over half of your plans are represented in your final products.
  • The most popular planning tool was ‘Short Product Plans’ (61%) and the least popular was ‘Market Requirement Documents’ (31%), though a few of you also mentioned ‘customer stories’ and ‘prototypes’ as key planning tools.

Watch this space for results from the next survey!

–Cameron

Written by Steven Sinofsky

March 21, 2013 at 10:00 am

Posted in posts

Tagged with ,