Evolving Web

Don’t Slow Down, Just Get It Done

My colleague and I were four days into a field exercise for an environmental impact statement or EIS. An EIS is a document every public project must complete to show what the short and long-term impacts would be if it were completed. They tend to be large and expensive. This particular project was very large and the impacts many.

Given that the project was underway and had a definite deadline, no one was willing to slow it down or change its scope. This particular task was supposed to take the two of us about a week to complete.

Four days into this particular task, we found the data we had been given was poor, the people to contact with better data were unavailable, and that the massaging of the new data we couldn’t even get would take weeks.

When we presented the managers of the project with this information, we were told Don’t Slow Down, Just Get It Done.

Get it done with what?

The data you already have.

We were then expressly told not to contact anyone else or extend this particular task.

Back then, we were completely confused as to why anyone would be so totally stupid. How could these managers knowingly ignore that we were using faulty information that would result in a useless report? These weren’t Dilbert characters, they were real live human beings.

Over the years I would watch other seemingly smart people drive their high-tech startups into the ground by insisting that an initial plan or idea go forward despite ample evidence that all that lie ahead was ruin.

What cognitive biases kicked-in to destroy these endeavors?

Irrational Escalation – This is in-for-a-penny-in-for-a-pound-ism. Once people start on a project, they find it very hard to stop – even if the project is obviously doomed or the return will not cover future costs. The managers felt that the project was already underway and even using bad data was better than delaying the project and asking for new data. The bad data (not surprisingly) later resulted in obviously flawed analysis – causing even more expensive and stressful work later in the project.

Expectation Bias – This is a world-view bias. If we believe something, we pick data points that support that expectation. Further, we expect that most data will support our expectations. We had an opportunity to create a research regimen that would yield scientific results. The managers assumed this was all a formality and that any data (good or bad) would support the original plan. This was likely underscored by “experience” that showed that most data did indeed support the original plans (which were likely suffering from expectation bias).

Planning Fallacy – A central issue here is simply that we didn’t have enough time to finish our task. The expectation bias inherent in the people who wrote the initial scope gave us only a week. This led to them, and us, falling prey to the Planning Fallacy which shows that human beings have a strong tendency to underestimate task completion times. On the ground, we saw this playing out. From the manager’s desk, the plan was correct, we were at fault.

Status Quo Bias – This bias says that once we start something, we tend to want it to continue. This is why in Collaborative Management we seek to build an explicit Culture of Continuous Improvement for teams and companies. Making change and improvement the center of the culture makes change the status quo. Needless to say, this wasn’t the case with my project back then.

The upshot here is that biases can gang up on us. Our enthusiasm, belief in ourselves, and assumption that things stay pretty much the same can combine to create seemingly logical decisions that can turn deadly. My managers no doubt reasoned that the project plan took over a year to write by well-informed professionals. There was very little cause for concern that a small part of the project might derail the whole thing.

In the end, our re-work was hardly noticed because other parts of the project became late, with much higher costs. One can only guess that the same forces were at work.

Collaboration over Process

(This is the first in a Daily Thoughts series. I used to blog every day, but during the writing of the Personal Kanban book and creation of the Personal Kanban website, I fell out of practice. This is getting back to true blogging. Fast, unedited, perhaps a little more politically incorrect here and there.)

 

The agile manifesto said "Individuals and interactions over processes and tools".  For years, I did not question that principle.

Now, however, I would replace this with "Collaboration over process."  Here’s why:

What's happened with agile is that the rhetoric is so team empowering that it transforms teams into heroes. Like individual heroes, this divides them from the rest of the org. It turns them into inward focusing groups that are optimized for their own product and have a well constructed but ill-fitting interface into the rest of the organization. While it was team collaborative and was more collaborative with outside stakeholders, the rhetoric still focused on the teams.

But the teams are made up of individuals. And the team operates within an organization. And the team has outside resources. And the team has clients. There’s a lot going on with those outside interactions that need to be explicit.

I really took the Agile manifesto seriously. Like many, it was pinned on my office wall. I could bludgeon uncooperative employees or clients with it. I could wax eloquent about it. For me, finding its shortcomings was a painful and lengthy process. I slowly came to the realization that, as it had aged, Agile had codified, ossified, solidified into something you could easily do wrong and that was nearly impossible to do right. The words in the manifesto no longer represented what was happening in practice.

So, I began to strip away some of the trappings of over-loaded agile at my company. We replaced sprints with release cycles. We destroyed the product owner for a fully collaborative relationship with clients. When we started with kanban, it was game-on. In 2005, when we ran our first kanban driven project, we had a very different view of kanban - but even then visualization of flow almost immediately started to change how we worked.

Our process evolved rapidly during that project. At every standup people had a suggestion of how to make it better. There was a collaborative spirit not just for creating the software, but also for how the project was managed. We were no longer following a rule-book of best practices. We were building something that worked for that particular team building that particular software for that particular client.

In other words, the team had the freedom to truly optimize.

Don’t let anyone say you are doing a process “wrong" – find what your “right” is.

Image by @gavintech and shared by Venessa Miemis

 

 

 
--

Spechetti

When coders have crazy unreadable code its referred to as “spaghetti code.” Single strands of code are impossible to trace through the tangled masses coders can weave. When this happens, it becomes incredibly difficult to understand the original intent of the code, the order in which changes were made, and how to go about making things better. This creates something known as “technical debt”. As time goes on, the difficulty in interpreting the code makes it time consuming and expensive to expand upon or to fix bugs.

It strikes me that this is very similar to the specifications that I have seen through the years. At project conception, one person might sit down and write a spec. Between conception and the start of coding, any number of people might edit that spec, introducing, editing, or removing features from the project. As the project begins and progresses, the spec is altered even more. Change orders occur. Off-line detailed conversations are hastily added to the spec or worse yet, included as an addendum. Soon we have spechetti - a document that has been through the hands of many, with differing intents, reflecting dozens of unrecorded conversations.

Spechetti creates a type of “legal debt.” Teams are required to satisfy difficult-to-decipher legal code that can be easily interpreted differently by others. Conflicts grow as interpretations diverge. Interpretations diverge the more granular (and difficult to find) operational clarity is in the spec. This makes the product time consuming and expensive to finalize.

The goal for projects should therefore not be to create a comprehensive spec that can be argued about at completion, but to create a legal and management system that actually drives agreement, clarity, and good business decisions while the project is in-flight. To do this, emphasis is placed on contracting for operational imperatives and not implementation specifics.

Existing contracting mechanisms create legal debt as a matter of course. We need a new kind of collaborative, non-punitive contracting system that replaces mounting legal debt with a mechanism that actually creates social, creative, and business capital.

Well, that sounds easy doesn’t it?

Tune in next time for what will kick off a series on Agile Contracting.

Portfolio Careers / Portfolio Lives

My friend and microbusiness partner Jeremy is a well-rounded guy. He has a few consulting clients that give him the income he needs to get by and maybe a little more. But that doesn't take up all his time. In his spare time he's also dancer, and with his wife and a few friends is opening a Montessori school. But that doesn't take up all his time, so he worked with two other guys and myself to create iKan, the Personal Kanban iPhone app. But that doesn't take up all his time either, so he got together with a bunch of other guys and created Crowdmap an awesome shared mind mapping tool for the iPad.

So Jeremy is, as I said, my microbusiness partner. iKan is a microbusiness. The application has helped many people take their Personal Kanban with them when they are away from their home or office. But it's also only $4.99. With four partners, it would take a very long time for any of us to become wealthy from it.

But what I'm noticing is this: The new entrepeneurs the media  keeps touting are not out building companies with just sweat equity. That is nothing new and completely misses the point of the transformation that is taking place.

The previous career models of "I'm going to get a stable job and go to the office every day" or "I'm going to launch a startup and we're going to become huge and make millions" are increasingly viewed as the self-defeating, zero-sum games that they are. People are recognizing that full time-work is fleeting; that at-will employment means you have no job security. And hopping from job to job is stressful and forces you to give up all self-control.

Instead, people are collecting portfolio projects with residuals that, over time, will result in reliable income streams. This is a vital distinction, because when you have a huge time-sucking job with no hope of residuals, every hour you spend working is worth a set amount – regardless of how much effort you put in or how much value you create. 

This means that trade-offs between the rest of your life and work will always fall in favor of work. If your boss tells you to work until midnight during your daughter’s recital, you need to work. If you don’t, the zero-sum game means you lose disproportionately to the cost of the action. Going to the recital will always lose to not having a job and health insurance. But the action that night at work compared to your daughter’s recital? That individual trade off was likely in favor of your daughter.

Building a portfolio of microbusinesses with an underpinning of paid project work means you are building both good short and long term income opportunities. For a portfolio holder, the option of working that evening or spending quality time with your daughter will, appropriately, come down on the side of the daughter – and if it doesn’t, it will be because the trade-off was really worth it.

So Jeremy and others I know are placing themselves in a position where they can exercise life’s options with the least amount of external costs. This allows them to build not only a portfolio of projects they have worked on, but also greatly expands the portfolio of projects they can work on. In doing this, Jeremy and others have bought themselves a great deal of freedom.

The next time you think about work/life balance, consider this: have I placed myself in a position where I pay a penalty for choosing activities outside of work? Have I placed a tariff on my own happiness? Have I left myself unable to work on projects that will make me money, expand my capabilities, and provide an interesting challenge? How many of my options have I closed off?

The original image can be found here by TheAlieness GiselaGiardino²³

Working with the United Nations

Over the last six months, Modus Cooperandi has had the good fortune to participate in three United Nations projects. The UN's missions lend themselves well not only to collaborative management, but to lean and social media, too. While the UN will be quick to admit they aren't early adopters of the last two methods, they are nevertheless appreciative of the power of lean and social media, and are ready to begin implementing them in earnest. It's been exciting and rewarding to watch, and we feel privileged to be a part of this work.

Our three projects so far have been:

Collaboration eLearning Packages

UN Food and Agricultural Organization - Rome, Italy

Modus Cooperandi worked with a team of 20+ authors, editors, and eLearning specialists to build a comprehensive set of lessons around collaboration, community, and team building. Jim and Tonianne helped devise a group writing system using a variety of online tools to facilitate communication and collaboration. Additionally, we were principle authors on three sections of the eLearning package itself. Once complete, the system will be translated into six languages, and made available to UN staff and those interested worldwide.

OzonAction's 2010 Social Media Plan

United Nations Environmental Programme, OzonAction Unit - Paris, France

OzonAction is the UNEP's group which, with the ambitious goal date of 2010, helped phase out the manufacturing of ozone depleting substances (ODS) such as chlorofluorocarbons (CFCs). Now, in its second phase, two additional ozone-depleting chemicals are on the chopping block: hydrofluorocarbons (HFCs) and MethylBromide. While OzonAction could certainly use their existing and successful methods to meet their deadline for the removal of these two compounds, they've chosen to incorporate social media to eradicate them ahead of schedule. Their success in the past has not made them complacent, and Modus Cooperandi is helping to create a social media plan that will provide the organization with actionable steps that won't overtax their budget or their staff. The goal here is to provide the maximum benefit for OzonAction without getting caught up in the fads or hype of the social media movement.  OzonAction's goals are serious, and so their use of social media should be directed in a way to reflect that sense of gravitas.

2010 Human Development Report for Vietnam

United Nations Development Programme - Hanoi, Vietnam

Over the past two decades, with the rise of globalization, Vietnam has experienced unprecedented economic growth. With one of the fastest-growing economies in the world, Vietnam has graduated to a mid-tier economic power. For this nation in transition, the current global economic downturn has left Vietnam with both options and opportunities. Countries in the United Nations need to provide a Human Development Report (HDR) to guide policy and funding both internally and externally. In many cases, the HDR can be several years between issues, and Vietnam is no different. For this project, UNDP and the Vietnam Academy of Social Sciences (VASS) have gathered researchers and scientists from several different agencies within and outside Vietnam to create the HDR. The goal of this project is to have a full-fledge HDR, with detailed and directed recommendations, ready for the Vietnamese General Congress in October. Modus Cooperandi is facilitating this effort by implementing a collaborative management system, coaching researchers on collaboration as the document is authored. Rather than merely having a document constructed of distinct sections authored by independent researchers, the goal here is to bring all the researchers together and inform the sections with one voice, and in real-time. This should result in an end-product that makes consistent points throughout, as opposed to individual points in each section. Recommendations will then be bolstered by coherent arguments threaded throughout the entire document.

Bigger Ears Make You Dumbo

Consider how the movement of a meme across the social media landscape spreads what looks good on the surface, but is fetid logic underneath.  A few months back I spoke at Social Media Breakfast, Seattle about Social Media, Lean and the CIA. A big part of that talk covered the danger of companies assuming that merely listening to people through Twitter was a standard of success.

Now let me tell you a little story about a recent experience I had with Delta Airlines, and how it relates to Chris Brogan's quote regarding assumptions on the Internet.

I was flying back to Seattle from Viet Nam. I had a ticket, but no seat assignment on the leg from Tokyo to Seattle. I was told that this wasn’t a problem, I could get one when I checked in at the desk in Tokyo.

My layover in Tokyo was nearly 10 hours long, before my 10 hour flight back to the States.

No problem, I thought. I would quickly check in, and then enjoy the day exploring the city.

I wend my way through the intricacies of Narita Airport, finally finding the transfer desk. It was unmanned. It was about 7 am at this point, so I went to the information counter and asked when the Delta people came to work. 

They told me 11:30.

Well, that’s pretty inconvenient. But I got myself some breakfast and proceeded to wait. 11:30 came and went, and yet there was still no one at the Delta transfer desk. A little after noon the desk finally opened. It took 15 minutes for them to process my request, after which they informed me I would get my boarding pass and seat assignment 15 minutes before departure.

I inquired why, and was told my ticket was so cheap I didn’t get a seat assignment. I said that this was leg four of a ticket that went from Paris to Beijing to Hanoi to Tokyo to Seattle and all the other legs had seat assignments. At that point I was told tersely that I simply didn’t have a seat assignment.

“Okay, how do I avoid having this happen in the future?” I asked.

I got my papers pushed back at me and never did receive an answer. I have no idea how to make sure this doesn’t happen next time.

So, I’m stuck in Narita for 10 hours now because I need to make sure that the moment they open the gate, I’m first in line for a seat assignment. I do what any red blooded netizen would do. I tweet that I’m annoyed with Delta.

The next day, Delta’s big ears hear my pain and tweet to me:

So they heard me.

And so I DMed them. Now…look up.

My story wasn’t short. But I had to mash it into several 140 character statements because Delta didn’t actually give me a higher bandwidth way to have the conversation.

I told them the fastest possible version of that story. Without any further communication, Delta gave me 2,500 frequent flier points. I don’t even fly Delta! This was pretty much the equivalent of Charlie Brown winning 5 free haircuts. “My dad’s a barber and besides, I don’t have that much hair to cut!” he lamented.

 Delta’s ears might have been big, but their execution sucked. No, their listening is not what I will remember them for, but rather, it is their consolation prize I will forever associate them with. I still have no idea how to not get stuck somewhere waiting for a seat assignment. That was all I really wanted: simple information.

What should Delta have done? Let me now share a story from an earlier part of that trip.

Due to a communication snafu, Orbitz messed up part of my flight. At one point, I was in real danger of being stuck in Paris with no way to fly onto to Hanoi or, to return home.

I tweeted my frustration and Orbitz responded within minutes.

They immediately gave me a direct email address and a phone number to Kristi, a real person, who could help (and who could take the time to get the whole story). Orbitz then fixed the problem I had and one other I didn’t know I had. Then they told me how I could avoid having that ever happen to me again.

Orbitz had big ears, but more importantly, they also had helping hands.

Delta’s system is built on productivity. They feel they did a good job by moving me through their process and giving me something. Orbitz is build on effectiveness. (I cover the difference in this post). They found the real problem, solved it, and made sure I was taken care of. Rest assured, both experiences will have a lasting impact.

(Oh, and Kristi later wrote to say she was glad I made it safely to Hanoi, and to thank me for the tweet.) 

Personal Kanban Discussed on the Business 901 Podcast

In late March, I had the good fortune to be on Joe Dager's Business 901 Podcast.  The topic, of course, was Personal Kanban. Joe edited the conversation into two parts which can be found below:

Part 1

Powered by Podbean.com

Part 2

Powered by Podbean.com

Building iKan Without Pain

In record time, the Apple Store has accepted our iKan Personal Kanban app.  This means that Modus Cooperandi’s first iPhone app is up and ready for sale. That link there tells you about the app itself, but this post is going to discuss how it came to be and why it is significant to me.

You see, the way things get built is changing rapidly. It’s exciting – but it’s also not surprising when it fails. But when it works, it is a beautiful thing.

Here’s what happened.

Over the last eight months, people kept asking me “Where is the Personal Kanban iPhone app?” I usually answered something like, “We just came out with Personal Kanban a few months ago, give me a break!” I was expecting other developers to do the iPhone app, but after a time it became clear no one was going to do it.

After a Seattle Lean Coffee, I found myself talking to Jeremy Lightsmith, Gary Bernhardt and Corey Ladas. We discovered a shared vision for what iKan would look like and how it might evolve. We were all keenly interested in the future of work and lean. Things clicked.

We negotiated a quick equity-for-effort model, designed to evolve with the product. As we move forward, equity stakes in the product will change as groups of us (or others) work on the product. No pain, no bickering.

The next day we had our first pre-alpha of the software. Everyone pitched in with the time they had and the expertise they could bring. Jeremy and Gary doing the coding. Corey and I finalizing the feature set and guiding the release plan. And finally Jeremy and myself getting all the rigmarole with getting Apple certification for the developers, Modus Cooperandi and the app itself.

We set up a dropbox folder where Jeremy and Gary fed versions of iKan to Corey, the beta testers (Thanks Ann and Patty!), and myself. We used a development kanban on Zen to track features, progress and tasks. All in all it was about eight weeks to completion.

Why is this beautiful? It was refreshing to have an idea, come up with the first minimal release for that idea, and just build it. No angels, VCs, loans or legalities. Just four people who wanted to get this thing out and working.

Between this, the Personal Kanban book and the work Modus has been doing with the United Nations, I’m feeling pretty good about the state of collaboration in my world right now.

Again, check out the iKan Personal Kanban app and maybe buy a few.

 

Social Media, Lean and the CIA

At the end of March, I spoke at Social Media Breakfast, Seattle (See their recap) at the Waggener Edstrom offices in Bellevue. They were live streaming the talk, but had some technical problems – so the video is in two parts. If you want to see what the audience saw on the screen, there’s also the Prezi I spoke from here.

This talk is covering the challenges that organizations have with collaboration, both internal and external. Social Media and Lean need to be applied together to provide both a set of principles and a collaborative foundation. I also talk about being a punk rocker.  So, if you want to know how punk rock, twitter and the CIA all mean the same thing … take a look!

Part 1 Part 2

Scotch, Apples and Time to Think

What does your company do?

Every company does something different, no matter how slight. Even Burger King and McDonalds have their differentiators.

These differentiators, and ones you've planned to release later, are vital to your survival. They make your products unique. If you pick the right differentiators and can communicate their value, you win! If you pick the wrong ones or can't communicate the value of the right ones, you may well lose.

Companies are filled with people. By and large, these people care about the company. Not only because they like having a job, but also because they are interested in their profession.

At Modus Cooperandi, we try to schedule specific times just to think together. Frankly, it's my favorite part of owning a company. When we were in the Lake Union offices, we had 3pm Scotch. We'd break out the single malt, some nice glasses, and just talk. No agenda was set, but these conversations were deep and engaging opportunities. We developed a lot of new knowledge from our 3pm Scotch.

When I was in DC, we instead took "apple breaks," or went for a walk. Whenever we'd hit a wall in our work, someone broke out the cutting board and knife we knew it was time to talk it out.

Modus' main product is intellectual - we manufacture ideas and knowledge. Whether we are writing a white paper or coaching individuals or teams, we are leveraging tools to help them better manufacture their own ideas and knowledge.

3pm Scotch

3pm Scotch was a time of invention. We'd gather, find a topic, and off we went. Many times there'd be a running theme that carried over from the previous day, but that theme evolved. The ritualized nature of these gatherings became part of the culture. Corey and I would start talking about something in the morning and one of us would suggest writing it on the white board "for Scotch."  We'd record it, and then get back to daily business.

This prevented that conversation from becoming a distraction at at 10am, and instead honored it as a legitimate business act at 3. It also gave us a specific time where we - as a company - took our manufacturing resources (our people) and focused them on new product development or product improvement. We didn't do this by forcing a particular topic, but instead by providing the time in the first place.

On separate occasions, both Thu An and Jeanine expressed how they'd been waiting for these moments all day. This had nothing to do with the Scotch (they often drank tea), and everything to do with something they were itching to talk about.

Software development and other knowledge work teams rarely do this. We get so buried in the day-to-day "work" that we forget what it is that we are building. We miss opportunities to make them better or sell them faster.

Apple Breaks

Apple Breaks often occurred like Andon events on an assembly line. When someone pulls an Andon cord in manufacturing, it is an instant alert that there is a problem, and a team quickly forms to solve it. In some cases, the pull of the Andon cord may actually stop all production.

Apple Breaks caused us to get away from our laptops, regroup in the kitchen, and discuss the problem we were facing. Tonianne and I would get away from our screens and instead focus on the issue, rather than on the words we'd typed. Tonianne likes to say "our nose is too close to the canvas." 
Apple Breaks not only forced us to focus on and solve the issue at hand, they also got our noses away from the proverbial canvas. They gave perspective. They gave us time to work it out.

Most importantly, Apple Breaks gave us permission to stop "working" in order to get work done. Permission is important here. When you are building something for a living, walking away from the production center feels like you are abdicating your responsibility. But this isn't the case.

Watch any construction project. The construction workers take regular breaks, and not just because their work is physically exhausting. It's because they know the more tired they are, the more likely they are to injure themselves. Sometimes walking away from the computer is the best way to use the computer.

Apple Breaks recognize that the source of many issues is often being stuck in the current form of the solution we are working on. The more we stare at that form, the more invested we are in it.  Walking away from it frees us of its tyranny. On more than one occasion, Tonianne and I solved a problem during a 20 minute Apple Break that we fought with for days on the screen.

Why Scotch? Why Apples?

You can eat or drink whatever you want - that's irrelevant. The point here is: Take time out to think expansively. Take time out to solve problems as they happen. Your people need permission to think. Give it to them.

Remember: Knowledge is your company's #1 asset and its #1 product. Knowledge comes from thinking. Did you really hire people to not think?