I find the leadership is really about storytelling. First, having the skills to survey the landscape, recognize the patterns, and choose an appropriate path and second, and perhaps even more important, the ability to paint that picture for those that you may lead. To make them see themselves as part of the story. To paint a picture for others to see begins with framing a scene and then showing it.

I first heard this quote from a minister at a Portland-area church event and thought it was fantastic. It applies in so many situations and is such a good reminder about human nature.

If you want to use the cartoon for non-commercial purposes, make sure to give me the props and linked back to http://jenniferbdavis.blogspot.com.

I am amazed that over the years one of the most popular posts I have done was on the topic of "Yes, and", the tool used by improv actors to create realistic scenes and engage their audience and fellow players. It is worthy of a review.

After you do, I invite you to click on the graphic above. Download it. Print it out. Post it in your cube or office. Something Hugh from GapingVoid calls "cube grenades." Put it on your bathroom mirror. Make it a constant reminder of how to build teams, cultivate a culture of collaboration, and how to have fun.

If you post it or use it for non-commercial purposes be sure to give me credit and link back to http://jenniferbdavis.blogspot.com.

My friend and coach, Julie Naster, posted a great article about the danger of getting facts and interpretation mixed. Things she calls "assertions" are statements of fact, like the weather is 45 degrees. "Assessments" are the judgements we apply to those, for instance "it is cold and dreary" or "it is crisp and refreshing."

If we collapse the two or confuse them, we are ruled by our unguarded thoughts instead of having mastery over them. This is the little collapse that can lead to an avalanche in our mood or perspective, trapping us below it.

When you catch yourself making a judgement statement today see if it is fact and if there are alternative explanations that might be more useful to you?

Photo by Nebulous1 on flickr.

Introducing..

We love movies and books that are based on reality. No matter how fantastic or unbelievable the events in the tale may be, it instantly has credibility if it begins with "this story is based on a true story." We are immediately drawn in. Real truth, even if sensationalized or dramatized a bit, is so irresistable.

In contrast, I give you the financial forecast. For those of you not involved in these types of things, financial forecasts are models that people build, usually in Microsoft Excel, that show projected revenue, profit, costs, and the like in an effort to track the progress of a business, to make decisions regarding strategy or tactics, and to communicate to others about the business (whether they be management, shareholders, partners, etc).

The thing about a financial forecast is that the future is unknown. A fact that we sometimes like to ignore. We can not predict the future. And as they say in Princess Bride, "Anyone that tells you different, Princess, is selling something."

So, because the future is unknown, you need to make assumptions. More like "make up" assumptions would be more accurate, as all forecasts are works of fiction. Those assumptions about customer acceptance, revenue growth, cost reductions, or the like have a huge impact on your perception of the business opportunity. They can have a huge impact on the short-term decisions that might be made. Assume a healthy economy and low product return rates and you can convince yourself to spend more in marketing, only to find out later that these assumptions were horribly wrong and the money was wasted. Assume that 20% of your products will be sold with a unique feature and if it turns out being 50%, you could find yourself with product shortages and unhappy customers. You could be off by a little or a lot. Assumptions are a killer indeed.

The best assumptions are ones that have a high probability of occurance. That high probability based on some past perforamance. If you always have a slow first quarter of the year, it safe to assume that next year will be no different. If you have a trend line extending back into time that says that revenue is growing, you have a reason to believe it will continue. Distrust step functions. There has to be reasons to believe.

It is just like the movies and books. We are drawn into the story if we believe it is based on truth. Same with financial forecasts. This is true in business, but also in non-profit organizations, churches, and even personal finance.

So, how do you create good assumptions:

1. As I have said before, trends trump step functions. In other words slow and steady trend lines are more probable than things that immediately get better overnight, like someone flipped a switch. If you are assuming a step function improvement, you better know exactly what switch is getting flipped and be confident in the outcome.

2. Understand and measure the key levers of the business for real-time feedback. If your business is dependent upon selling service contracts along with product sales, you should know what your attach rate should be and what it has been. You should be able to see the actual attach rate trends as frequently as is reasonable and should share them with the teams involved. You should know where your costs are and the boundary boxes in which things should stay for the business to be profitable. As the good folks at GE taught us, "what you measure, you improve."

3. Everyone is in the business. This means giving your employers and partners visibility to the key metrics of your business will make you more successful, as choices are made at every level of the organization that greatly impact the success of the business and the factors you are measuring. Now, I am not talking about disclosing financial information inappropriately or giving away company secrets. I mean teaching all the players in the game how the score is kept, how to read the scoreboard, and their role in putting points on the score board. Remain open for anyone on the team to suggest a better play to call to reach the goal, once they understand the rules of the game. These kinds of conversations are the basis of true teamwork.

"For a list of all the ways technology has failed to improve the quality of life, please press three." - Alice Kahn

I love technology. I especially love database-driven, web-enabled technologies with great interfaces that make important things easier to do. Seriously, I really do.

But, I have become aware recently (or should I say "reminded") of ways in which technology can fail to deliver on its promise.

1. Stop-Drop-and-Roll When Technology Makes Something Simple More Complex

Forget scale. Forget extendability. Sometimes business needs are simple. You need to answer the phone and route calls, for instance. How hard can it be really? Incredibly difficult once you create phone trees, voice prompts, scripts, and queues. Add to that a hold music music track from Hades (a stress-inducing piece of classical music that is reminiscent of a battle scene from an epic film) and you have a comic combination of making something simple hard. Part of the problem is trying to fit all possible needs into one solution, when in fact a customer-driven approach would call for multiple, smaller solutions.

For example, some websites are packed with information for everyone which makes them hard to navigate, contain too much copy, and lose their purpose (for example see anything that the good folks at Microsoft post), so all technologies are prone to this kind of complexity. In contrast, stands very simple web page design where the text is a clear call to action, the copy is natural speech, and all of the content fits "above the fold" without making the user scroll to read.

Using the web page example and applying it to my telephony problem, I wonder if the solution is this. Replace the complicated phone tree with its 50 options (and the hold music that enrages already irritated callers) with a pleasant woman's voice who says "Thanks for calling us. We love to hear from you and want to make sure you talk to the right person who can help you the best. To skip to sales, press 1. To go straight to technical support, press 2. Or just hold and a real live, honest-to-goodness human being can assist you. On our website you will also find a directory of contacts that might help you connect even more quickly. Again, thanks for your business. Please wait a moment while we connect you."

If technology makes something more complex, you should stop it, drop it, and roll with something new. For instance, if your customer base is known and finite and if you have more than 2 options on any phone line, break it up and pass out new numbers. It could be that your business is too complicated for the technology to solve. This leads to my second principle.

2. Don't Pave a Cow Path (or Pave Only Cow Paths that Lead Somewhere)

A colleague of mine once told me a story about how a farmer sold his property to a developer and they decided to build houses along gravel roads laid down where the well-worn paths through the pasture land that the cows had cut over years of grazing. Years later, they paved those gravel roads and although the residents complained, only the old-timers remembered the someone hadn't sat down to design the best layout for the neighborhood, but had instead paved the cow paths.

How often do we do this? Come up with a great technology solution to a problem we don't understand fully, just because the technology solution is in hand or can be envisioned. I am guilty of this more than I like to admit (being generally optimistic about technology and life and having this natural impatience to get on with something already). We start building solutions for things that only work the way they do by accident. Or, we throw out a perfectly good "cow path" solution in favor of a more complicated one.

One of the most successful development projects I was involved with was an internal corporate application. Before writing a single line of code, I lived the workflow of the application (however painful it was) for several months managing an Excel spreadsheet. During this "alpha" phase, I worked out all the communication flows and templates, the policies of who needed to be copied on what, and started to quantify the benefits of automation. The core workflow changed quite a bit in those early days and got refined in this manual process, and I was able to articulate requirements for a little application that is still very useful and powerful (and has gone through numerous iterations as new needs and ideas were explored).

This reminds me that one must make careful choices about what gets paved and why. Living in a tent on a cow path for a while, while taking land surveys might be a perfectly reasonable way to "write" requirements.

3. Nothing Replaces an Outside-In View

Companies love to create Inside-Out solutions. You need to know how many product returns you get and why products fail, so you adopt a nifty little service application to manage the transactions. It works great. Unless, a customer wants to see all their transactions and the status of each. Maybe that gets a little tougher. Or unless a sales person wants to see all their transactions and the status of each, across multiple customer accounts, geographies, product lines, or departments. Then the transaction system doesn't quite serve the purpose. Before you rush out an implement a fully-integrated CRM package (which can be wonderful by the way), remember the problem you are solving and the points above. It could be that the outside-in perspective would tell you to keep the transaction system and implement a report instead. It could be that a fancy, automated report isn't needed, but rather a regularly scheduled phone conference with a key customer to walk them through any open issues and assure them of your attentiveness to their issues. It could be that you have back office communication or coordination challenges, that once solved through better roles and responsibilities, the issues are minimized and more manageable.

It is good to keep in mind that most customers don't really care about the efficiencies of your business overall, how the same phone tree helps them and their competitors, or what you are doing to solve problems for everyone. They really want their problems solved. And, it is always easier to solve one issue than ten.

Technology can be a part of that. It can help coordinate information, make dispersed and diverse team act together, and can provide feedback loops in real-time. It can be game changing or tactical, but it is only a part of the whole solution.

I just received a great little article by Patrick Lencioni, an author who I highly recommend. You can sign up for their newsletter here. It was about the design of office spaces and how it affects employee interaction.