What does a Growth Engine involve? (Part 4: Components)

This is the fourth and final part of a multi-post article, which explains what’s involved in a Growth Engine.

Action: A general term for any performance executed by a human or non-human mechanism (this includes all processes, workstreams, operation sets, and their constituent components).

Module: A discrete functional unit that receives inputs to be processed using a collection of actions to produce a specific output. Modules have connections as needed for linking with interactions, integrations, and other modules. Modules can be created from templates or produced bespoke. Modules are used to facilitate quicker Growth Engine construction.

Interaction: An input/output exchange between actions, between modules, and between actions and modules.

Integration: An automated interface for data exchange between different software applications allowing output from one application to be automatically used by another application.

Scheduling: This is the action that incorporates time into the Growth Engine. It is used to set the pace of actions and plan their execution, intervals, etc.

Tangible system: A physical system constructed of tangible components, such as a computer system. Such systems most often have intangible guidelines and operational concepts.

Intangible system: A conceptual system consisting of intangible components, such as a problem-solving system. Such systems most often have tangible tools and job aids.

Journey: A grouping of related workflows, operation sets, and processes designed to achieve high-level strategic or governance objectives. Examples are the customer journey and the employee journey.

Process: A specific sequence of steps that may consist of human or non-human actions or both with a specific outcome. (This may involve one or more workflows, operations, etc.)

Recipe: A recipe is a formula for creating a Growth Engine function to achieve a specific business objective. A recipe consists of a combination of modules, interactions, integrations, systems support, workflows, disciplines support, etc., applied in a systematic way to achieve the desired result.

Growth Engineers collaborate with clients to create bespoke recipes and then follow these recipes to create the blueprints that are followed when building out the company’s Growth Engine.

For example, if a client wants to improve the quality of hires for a specific role, a bespoke recipe for doing so for that role will be developed. This recipe will be created following the systems thinking concept and include all of the elements and factors, as well as how they should be implemented, that are necessary to achieve the set objective in an effective, sustainable way.

Culture: Building a great culture is the ultimate output of a full-fledged Growth Engine.

Culture is “who” a business is. Culture is how a business believes, behaves, and reacts. It’s not the lip service, the PR, the spin. It’s what is thought, said, and done behind closed doors, in private gatherings, and when others are not looking.

A great culture is consciously designed, built, and sustained. It requires constant watering, fertilizing—and weed pulling. It must be fed with nutritious principles and best practices. It requires real-time monitoring, short-term improvement sprints, and long-term vision.

A great culture trumps all—it’s better than any one individual and will outlive all individuals.

A great culture is like a great civilization—it’s the ultimate competitive advantage.

Non-Human Actions

Operand: An action performed by a non-human mechanism that is part of an operation.

Routine: A series of operands performed by a non-human mechanism.

Operation: A specific sequence of steps consisting of operands, routines, etc., with a specific outcome taken by a non-human mechanism. (This may be all or part of a process.)

Operation Set: A grouping of related operations that collectively produce a specific outcome. (This may be all or part of a process.)

Human Actions

Task: An action performed by a human that is part of a procedure.

Procedure: A series of tasks performed by a human that is all or part of a workflow.

Workflow: A specific sequence of steps consisting of tasks, procedures, etc., with a specific outcome followed by an individual. (This may be all or part of a process.)

Workstream: A grouping of related workflows that collectively produce a specific outcome. (This may be all or part of a process.)