HomeCurated Articles for EntrepreneursHow Does the Simplex Process Organize Continuous Creative Problem Solving?

How Does the Simplex Process Organize Continuous Creative Problem Solving?

Better Thinking, Planning, and Leadership for Entrepreneurs

The Simplex process organizes creative problem solving into a cycle that continues through implementation. It begins with finding a problem, develops an evidence-based definition, generates and evaluates ideas, and connects a selected solution to planning, acceptance, and action. The sequence matters because an attractive idea can be irrelevant to the actual problem, and a well-chosen idea can remain unused if implementation is never organized.

The version presented in the supplied Mind Tools document follows eight stages associated with Min Basadur’s work. Basadur’s current description of the process uses the stages problem finding, fact finding, problem definition, idea finding, evaluation and selection, planning, acceptance, and action. These stages connect exploration with decisions and execution. The framework is a process for working on a problem, rather than a formula that supplies the answer.

Finding and Defining the Problem

Problem finding identifies a situation worth examining. A business may observe repeated customer confusion, a growing backlog, or a service that customers request but cannot currently obtain. At this stage, an observation can begin the work without already containing a precise diagnosis.

Fact finding develops the account of that situation. The relevant evidence depends on the question. Customer messages can explain what customers report; transaction records can establish when events occurred; direct observation can show how a process operates. These sources contribute different information and can be compared without treating every opinion as a measured fact.

Problem definition then states what the work is intended to address. A statement that the business needs a new website already selects a type of solution. A statement that customers cannot determine which service fits their request defines a problem that could have several solutions. The difference changes what the next stage is allowed to consider.

Consider a hypothetical small business selling specialized maintenance services. Customers frequently request quotations for services that do not match their equipment. The owner initially proposes redesigning the website. A review of inquiries shows that the difficulty concerns identifying equipment models before a quotation can be prepared. The problem is narrower and more specific than the original proposed project.

In that example, the new definition does not forbid a website change. It places that change among the possible responses to a defined information problem. A telephone intake script, a model-identification guide, and a revised request form can also be considered because they address the same underlying task.

Generating Ideas Before Selecting One

Idea finding develops possible responses to the defined problem. The distinction between generating and judging matters because an early criticism can end consideration of an idea before its useful element is understood. Separating the activities allows a proposal to be described before the group decides whether it meets the relevant criteria.

In the maintenance example, participants might suggest requesting a photograph of the equipment label, offering an identification call, or providing examples of where model numbers are located. These hypothetical ideas have different operating requirements. At the generation stage, the task is to identify how each could help obtain the information needed for a quotation.

An incomplete idea can also become part of another idea. A photograph request might be combined with a short explanation of which part of the equipment to photograph. The combination addresses an ambiguity that the original request leaves open. This is a concrete development of the proposal rather than a general judgment that the idea is good or bad.

Generating alternatives does not require every idea to survive. It creates material for comparison. The definition of the problem remains the reference point: the alternatives concern obtaining usable equipment information, not adding unrelated features to the business.

Evaluating Alternatives Against the Actual Task

Evaluation makes the basis for selection explicit. Relevant criteria in the hypothetical business might include the accuracy of equipment identification, the effort required from customers, staff handling time, and compatibility with existing communication channels. Each criterion corresponds to an activity or consequence that can be examined.

The alternatives may perform differently on those criteria. A telephone call allows clarification but requires simultaneous availability. A photograph can be reviewed later but needs sufficient image quality and the correct subject. A web form can standardize information but may not resolve a customer’s uncertainty about the equipment itself.

The comparison can lead to revision rather than immediate rejection. If a photograph is useful but customers often send the wrong view, an example image or a specific request can improve the proposal. Evaluation then applies to the revised version. The selected solution becomes more defined through the process.

The decision can also distinguish different customer situations. A photograph route may serve one group, and an identification call another. That is a specific operating choice if the conditions for each route are stated. It is different from keeping every alternative simply to avoid making a decision.

Planning the Selected Change

Planning translates the selected approach into work that can be carried out. The maintenance business may need wording for the request, a place to receive photographs, a staff procedure for checking them, and a response for cases that remain unclear. Each component has an output and a relationship to the rest of the process.

The plan can identify sequence as well as responsibility. Staff cannot follow an agreed procedure before its decision rules are defined. A customer message cannot accurately describe a process that has not been specified. Dependencies make the order of preparation part of the plan.

Resources also become concrete at this point. Staff time spent reviewing images is an operating requirement, not merely a detail of website design. If the selected solution adds work to an existing role, the plan describes that work and its timing. This connects the proposal to the people who will implement it.

A limited initial application can have a defined scope and measurement period. In the hypothetical example, the business might apply the revised intake process to one service category and examine the resulting requests. The scope is part of the plan; the outcome must come from the actual records rather than an assumed improvement.

Building Acceptance Through Specific Understanding

The acceptance stage concerns the people whose participation affects implementation. They may include employees who perform the work, managers who allocate resources, and customers who supply information. Their questions can identify requirements that an abstract proposal does not reveal.

Acceptance is more specific than a general statement of support. A staff member may agree that better equipment information is useful but need a clear rule for handling unreadable photographs. Another may need to know when an inquiry should move to a telephone call. Resolving those questions changes how the solution can operate.

The process can also expose differences in what participants think has been agreed. One person may expect every customer to use the web form; another may expect email to remain available. A defined operating arrangement makes those assumptions visible before they produce conflicting customer instructions.

The supplied Mind Tools account describes this stage as selling the idea. In practical terms, the work includes explaining the proposal and addressing the concerns of those involved. The current Basadur description uses acceptance. Both labels point to the transition between a selected plan and participation in carrying it out.

Acting and Observing the Result

Action puts the selected arrangement into use. The revised message is sent, staff follow the procedure, and requests are handled through the agreed channels. Those events distinguish implementation from the completion of planning documents.

The result can then be compared with the original problem. In the hypothetical maintenance business, the relevant observation is whether incoming requests contain enough information to identify equipment and prepare quotations. A more attractive form is not the same outcome. The problem definition supplies the basis for judging what changed.

Operational records can separate several effects. The revised approach may reduce clarification messages but increase time spent reviewing images. It may help with one equipment family and have little effect on another. Those are specific results that can guide the next cycle when observed; they are not outcomes established by the hypothetical example.

A change can also alter the problem being addressed. Once equipment identification becomes easier, quotation preparation might reveal a different delay. The next investigation begins from that observed situation. The cycle continues because implementation changes the conditions under which the business operates.

Keeping the Stages Connected

The stages are distinct activities, but they are not isolated compartments. New evidence can lead to a revised definition. Evaluation can improve an idea. Planning can reveal an operating dependency that changes the selected design. Returning to an earlier stage can be a response to specific information rather than a failure to follow the process.

A record of decisions helps preserve those connections. The reason for selecting a photograph request, the conditions under which a call is used, and the outcome being measured belong to the same account. Without that connection, a later change can preserve the procedure’s appearance while losing the purpose it was designed to serve.

Simplex also separates participation from authority. Several people may contribute observations and ideas, but the business still needs clarity about who selects the option, allocates resources, and approves implementation. The framework organizes thinking and action; it does not automatically assign those organizational responsibilities.

The process can distinguish a decision to gather information from a decision to implement a solution. During fact finding, an interview or record review produces evidence. During action, a revised procedure changes operations. Both involve activity, but only the latter puts the selected solution into use.

That distinction helps interpret an early pilot in the hypothetical maintenance business. If the pilot is designed to learn whether customers can supply usable photographs, its immediate output is evidence about that question. If the process has already been selected for normal operation, the same photograph request becomes part of service delivery. The purpose and status of the activity determine how its result is described.

Evaluation criteria can be recorded before comparing the strongest candidate ideas. This establishes why one option is preferred. If the criteria change after discussion, the reason for the change can be stated. The record then explains the decision without presenting a preference as an inevitable consequence of the method.

Participants may also identify different constraints. A customer-facing employee may understand the kinds of questions customers ask. An operations employee may know which equipment details determine the service. Combining those observations can improve the definition of the information required. The contribution is specific knowledge, not simply a larger number of participants.

The selected solution can preserve that knowledge in the process itself. A request for a model number can explain where it is commonly found and what to do when it is unreadable. The procedure then reflects the observed difficulty that prompted the investigation. Its details are traceable to the original problem.

Review closes that connection by examining the outcome for which the change was selected. If the business measures only how many forms were submitted, it may overlook whether the forms contained usable equipment information. The outcome measure needs to describe the intended operational change. That continuity connects problem definition, selection, implementation, and the next cycle of inquiry.

The process ends a cycle with an implemented change and an account of its effect. In the maintenance example, the chain runs from unsuitable inquiries to equipment identification, alternative intake methods, a selected procedure, and observed quotation readiness. That continuity is the framework’s practical contribution: a creative idea remains connected to the problem, the evidence, and the work needed to put it into use.

YOU MIGHT LIKE

WEEKLY NEWSLETTER

Subscribe to our weekly newsletter. Sent every Monday morning. Quickly scan summaries of all articles published in the previous week.

Most Popular

Featured

FAST FACTS