Put up or shut up: The corporate guarantee

By Gene Tanski, CEO, Demand Foresight

Things were getting heated at the sales meeting. The cause of my anger was an old theme: Industry-wide, client expectations for business software were so low that stories about the failure of big enterprise projects had practically become wallpaper.

Where were the repercussions for the business performance that never materialized? The big systems failed to deliver what they were supposed to over 70 percent of the time and the big checks just kept getting cut with no accountability. The whole dynamic needed to be nuked.

In the heat of our discussion about the institutionalized negligence of our gigantic competitors and how we could exploit it, a 25-year-old, Xbox-playing member of our team, said: “Dude, if we’re that bitchin’, why don’t we guarantee it?”

“What?” I asked him.  “Are you nuts?  Do you have any idea how software works?”

“No, not really. But I hear you guys constantly complaining about how everyone else over-promises and under-delivers. Why not do something about it?”

That simple dare became our biggest differentiator – and, more surprisingly, revolutionized the way we run our company.

During the dot-com boom, new businesses were founded on completely new thinking by young professionals, unencumbered by any notion of what was or wasn’t possible. Most of that potential was never realized, though – at least not in the first wave, since the young visionaries had no grounding in the disciplines that would sustain their visions over time.

However, we wondered, could our team fuse the experience of the old hands with the “anything is possible” optimism of our young teammate?

Once we got our minds around the concept, the experienced guys on the team were able to adjust some long-held assumptions and work through how to handle the risk, build the pricing and generally operationalize the concept.

It was a little bit like learning how to fly, as characterized by Douglas Adams in his “Hitchhiker’s Guide to the Galaxy” books: the key to flying was to throw yourself at the ground really hard, and miss.

It was exhilarating. I felt like we had just missed the ground by a huge margin, and instead were flying straight to a business model that embodied the exact opposite of everything we hated about the IT and consulting world.

The guarantee was an explicit one – with no wiggle room. Clients would measurably improve their business performance — in our instance, a 25 percent minimum reduction in absolute forecast error — or we wouldn’t get paid. Not a dime.

It could have been a disaster, but taking this leap of faith actually did incredible things for our organizational focus – and ultimately helped cement our culture and internally align all divisions of the company.

The developers know that the software has to work and be relevant to specific job responsibilities or they don’t get paid. Implementation and technical support? They better get it right or they don’t get paid. Sales people? They had better understand the client problem and know exactly how to solve it, or … well, you know…

Another benefit of this ‘put up or shut up’ philosophy was the elimination of the need to micromanage. Once everybody understood that the promise would not bend, I found I could trust everyone to solve problems the way they thought best.

Vacation policy? Didn’t need it. Our team was entrusted to take the time off that they knew they could afford to take. Office? Wherever they could open a laptop and do their best work. This culture tells us a lot about the kind of people we should hire — can they stay motivated and productive in our unique environment?

So an energetic, passionate clash of skilled professionals turned out to be lightning in a bottle. It let us fuse the brashness of youth with organizational know-how.

We still argue in meetings, of course. But these days I enjoy it. You never know what sorts of benefits it can produce.

This post first appeared on Venture Beat: Entrepreneur Corner on October 26, 2010

Demand planning vs. forecasting vs. management: an agreement on terms (Pt. 3)

There are a number of terms that are used when discussing demand forecasting, demand planning and demand management — all of which appear to be used interchangeably. Just what are we talking about here? I thought it would make sense to share the terms I use on this blog and at Demand Foresight,  and  articulate the difference between each.

In my previous two posts, I delineated what demand planning and demand forecasting mean to our industry. Lastly, there’s demand management.  We’re hearing this term a lot these days as it relates to the current economic environment. In economics, demand management is defined as the art or science of controlling demand to avoid a recession. For our purposes, demand management is the art and/or science of matching product supply to demand. If a huge snowstorm is forecasted to hit the Northeast, do the Home Depot stores in the region have ample supplies of snow shovels?  It is within demand management that total demand (open orders plus forecast) is matched against capacity to ensure an efficient and profitable approach. Getting this right requires cross-functional senior leadership as this is where revenue and margin meet.

It is important for an organization to understand the distinctions between demand planning, demand forecasting and demand management so that it can determine where it needs to focus in order to achieve substantial and measureable improvements in bottom-line performance.

Demand planning vs. forecasting vs. management: an agreement on terms (Pt. 2)

There are a number of terms that are used when discussing demand forecasting, demand planning and demand management — all of which appear to be used interchangeably. Just what are we talking about here? I thought it would make sense to share the terms I use on this blog and at Demand Foresight,  and  articulate the difference between each.

In my last post, I talked about demand planning. Next up is demand forecasting.  Based on the demand plans, how do we quantify demand?  And at what level?  The key is defining the execution level required for the forecast.  What is the correct level of detail in order to create efficiencies throughout the supply chain?  Is it at the SKU level?  At customer by SKU?   Once greater accuracy is obtained at the execution level, the same forecast can be aggregated to higher levels for use by multiple groups, including the CFO.  Demand forecasting can sit anywhere in the organization depending on cultural and organizational design fit.

Demand planning vs. forecasting vs. management: an agreement on terms (Pt. 1)

There are a number of terms that are used when discussing demand forecasting, demand planning and demand management — all of which appear to be used interchangeably. Just what are we talking about here? I thought it would make sense to share the terms I use on this blog and at Demand Foresight,  and  articulate the difference between each.

Procedurally and philosophically, we start with demand planning.  Demand planning is articulating what a company is going to do to create and shape demand.  Typically, this is driven and owned by sales and marketing within guidelines provided by the C-suite.  This can include everything from special ads that run in the Sunday circulars to in-store promotions with specific retailers. This discipline focuses on where to meet your customer and other go-to-market strategies.