Project ≠ Product ≠ Business ≠ Company

9. Februar 2020
Kategorien
Newsletter abonnieren

Project ≠ Product ≠ Business ≠ Company

Last few weeks I had a number of heated discussions around these terms. People get confused and make wrong decisions because of this.

This is my take on it.

A project is a temporary endeavor undertaken to create a unique product, service or result. It is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.

And a project is unique in that it is not a routine job, but a specific set of jobs designed to accomplish a singular goal. So a project team often includes people who don’t usually work together – sometimes from different organizations and across multiple geographies.

Where each project is unique, doing projects is something that is recurring. Most organizations spend a lot of time and money on projects.

That is why investing in project management capabilities gives you usually a high ROI.

A product is something that you can build and sell, directly or indirectly. It is the «thing» (though it can be a service) that you could make money from via a business. By itself, though, it won’t make money.

Typically the first version of a new product or service is the result of a project. The second version is usually not.

A business is a set of people, processes, and tools that have been structured around a product or service to enable it to make money.

Ideally, a business is profitable, but it may not be.

Ideally, a business doesn’t depend on any specific person being a part of it (including the founders), but it may rely on some exceptional people.

You can’t run a business solely with projects. You need day-to-day operations.

A company is an organization of people that is designed to run one or more businesses successfully and to create new businesses to respond to opportunities in the marketplace.

This must be, ultimately, independent of any specific employee, since companies, unlike products and businesses, are (or should be) built to last for decades.

A business is worth much more than the product that it sells.

A company is worth much more than the business that keeps it alive.

This is one good rationale for why some startups (e.g. WeWork, Facebook, Twitter), operating in environments where it’s easy to raise money, have bypassed the «build a business» step to go straight to building a company.

The danger with that is that if you don’t first build a business, you might end up building a company that’s incapable of building new businesses – and that’s not worth a whole lot.

In a nutshell: Project ≠ Product ≠ Business ≠ Company

Tags

Das könnte Sie auch interessieren

Project Failure Is Largely Misunderstood

26. November 2020

For many years, organizations, researchers, and practitioners have analyzed how to manage technology projects successfully.  Among them is the Standish Group, which regularly publishes its findings in its Chaos reports. In 1994, Standish reported a shocking project success rate of only 16 percent; another 53 percent of the projects were challenged, and 31 percent failed

Weiterlesen

User Enablement is Critical for Project Success

14. November 2020

Any system is only as good as how well it is used.  If it’s a CRM, ERP, or any other system, when users don’t know how to use the system effectively the benefits of the new system for your organization will be small, or even negative.  This means user enablement is critical to the success

Weiterlesen

The True Cost of Excluding Executives from the IT Decision Making Process

18. Oktober 2020

Throughout the past 15 years that I’ve been working as an independent project recovery consultant and interim CIO, I have observed executives’ frustration – even exasperation – with information technology and their IT departments generally. Some of the more common refrains are:  “I don’t understand IT well enough to manage it.”  “Although they work hard,

Weiterlesen

What Executives Need to Know About Project Management

11. Oktober 2020

I work exclusively with executives and when there is one thing that I have learned over the years is that effective executives have at least a basic understanding about project management and their roles in it.    When you look in a dictionary for the word «executive» you will find an entry similar to the

Weiterlesen

Project Inputs, Activities, Outputs, Outcomes, Impact and Results

27. September 2020

Many people and organizations seem to have serious trouble separating between the inputs, activities, outputs, outcomes, impact, and the results of a project.    This leads to lot’s of confusion, bad communication, disappointed project teams, and disappointed stakeholders.   Below you will find my take on these terms and their relevance for your project.  

Weiterlesen

Solving Your Between Problems

30. August 2020

Most executives agree with me that the biggest problems are not within roles but between roles.    Not within teams but between teams.    Not within departments but between departments.    And not within organizations but between organizations.     Such “between problems” are not assigned to anyone. Why? Because they are between.    And these

Weiterlesen

However Beautiful the Strategy, You Should Occasionally Look at the Results

6. Juli 2020

The title of this article is frequently credited to Winston Churchill (1874-1965), but he never said it. The saying first appears from about 1981, many years after Churchill’s lifetime.   The saying is used to stress that one needs to look at results and shouldn’t fall in love with one’s designed strategy if it doesn’t

Weiterlesen

Your Risk Matrix Is a Lie

15. Juni 2020

Risk management is at the core of good project management.    Or as Tim Lister says “Risk management is project management for adults”.     The standard approach is to use a risk matrix to classify project risks based on their probability and impact, then give each one a ‘risk score’ by multiplying the two numbers.

Weiterlesen

Most Good Strategies Are Not Planned

7. Juni 2020

Many people are discussing strategy and strategizing as if they were the sole outcome of a rational, predictable, analytical process.   But reality is often the opposite; emotional, unpredictable, and chaotic.     How organizations create and implement strategy is an area of intense debate within the strategy field.   Famous researcher on management and strategy

Weiterlesen

Is Your Strategy Bad? A Simple Checklist

26. Mai 2020

Recognizing good strategy is hard.    You need to understand the organization, the market(s) it is operating in, its competitors, its strengths, and its challenges.    On the other hand, recognizing bad strategy is easy.    Richard Rumlet coined the term “bad strategy” in 2007 at a short Washington, D.C., seminar on national security strategy.

Weiterlesen