INVO
Talk to an ExpertTalk to an Expert
Discovery & Process Mapping

First we learn how your operation really runs.Only then do we configure the system.

Before INVO is set up, we learn the way your organization actually works. We map processes, roles, data, systems, decisions and exceptions, compare them against the INVO Process Library, and design the target operating model with you.

Book a process workshopSee the Process Library
  1. Your operation todayProcesses · people · data · systems
  2. Process discoveryWorkshops, or recordings of the real work
  3. AS-IS mapHow the organization actually works
  4. INVO Process LibraryA reference model that already exists
  5. TO-BE processesThe target way of working
  6. INVO rolloutA system configured for the agreed processes

Process discovery

Tell us how you work.Or simply show us.

A process written into a procedure rarely looks like the process people run every day. So we can learn your operation two ways — in workshops with your team, or by studying recordings of the real work.

You pick the method that fits your organization. The two can also be combined.

Option 01

Process workshops

Tell us how you work.

In a workshop we walk through real working scenarios with your team, step by step. We ask about the data used, the systems involved, who is responsible, which decisions get made, what the exceptions are and where the process hurts.

What we look at

  • Process stepsWhat does the user do, in what order?
  • RolesWho performs the task and makes the call?
  • DataWhat information do they need?
  • SystemsWhere does each action happen?
  • DecisionsWhat determines the next step?
  • ExceptionsWhat happens outside the standard path?

Works best when you want to learn the process, ask questions and discuss improvements at the same time.

Option 02

Recording the real work

Show us how you work.

A user records their screen while doing their normal day. From the recording we reconstruct the actual course of the process — the data they receive, the systems they use, the decisions they make, who they message, and what their work produces.

What we can see

  • Data sourcesWhere does the information come from?
  • Systems and platformsWhich tools do they switch between?
  • Manual workWhat gets retyped, copied or recalculated?
  • CommunicationWhen do they email or call someone?
  • DecisionsWhat do they base the next action on?
  • WorkaroundsWhere do spreadsheets and email fill the gap?

Works best when you want to see the real course of a working day without reconstructing the whole process in a workshop.

One recorded morning

What buying a motor lot actually looks like.

Forty minutes of one buyer’s morning, as the recording shows it. Four of the eight steps happen outside the system.

Purchasing a motor lot — recorded session40 min
  1. 08:12
    RequirementThe buyer receives a spreadsheet of shortages for the build.
  2. 08:17
    CheckChecks availability in the current ERP.
  3. 08:24
    Supplier portalsLogs into two supplier portals and compares lead times and prices.
  4. 08:31
    ComparisonCopies the prices into a spreadsheet. Manual work
  5. 08:38
    DecisionPicks a supplier.
  6. 08:41
    OrderEnters the order on the supplier platform. Data entered twice
  7. 08:47
    EmailSends a confirmation to the manager. Process outside the system
  8. 08:52
    UpdateUpdates the status in the spreadsheet. Duplicated data

We do not only ask what the process looks like. We can watch how it is actually performed.

We don’t start from a blank page

Your processes are compared against a working INVO operating model.

Process discovery does not mean inventing every process from scratch. For the areas INVO covers we already have a mapped library of reference processes — from BOMs and planning through purchasing and inventory to production, quality and logistics.

INVO Process Library

  • Sales & customers
  • Engineering & BOMs
  • Planning
  • Purchasing
  • Suppliers
  • Inventory
  • Production
  • Quality
  • Logistics

Reference process steps

Purchasing
  1. 01Generate the requirement
  2. 02Plan the purchase
  3. 03Select the supplier
  4. 04Create the order
  5. 05Approve the order
  6. 06Confirm the delivery
  7. 07Handle shortages
  8. Every domain in the library opens the same way — a reference chain you adjust rather than invent.

Process fit

Your way of workingplus INVO experience.

We put the two side by side and decide, process by process, what to keep, what to simplify and what to build around you.

Your processes

How you work today

  • Your roles
  • Your requirements
  • Your exceptions
  • Your systems

INVO Process Library

How the process could look

  • Ready-made processes
  • Best practices
  • Automations
  • Rollout experience
Keep

This already works.

The process matches the standard INVO way of working.

We configure the ready-made workflow

Simplify

We can do this with fewer steps.

We remove redundant steps and manual work, and use what can be automated.

We design a leaner process

Adapt

This one is specific to you.

A business, program or contract requirement calls for a different course.

We adapt INVO

The Process Library gives us a starting point. It is not a rigid template your organization has to fit into.

Process design

We don’t map processes to produce a diagram.

The point of the analysis is to design the target way of working — simpler, more consistent, and using what INVO can automate.

Today — AS-IS

Buying components

Ten steps, four systems, no single status.

  1. Production schedule
  2. Requirement spreadsheet
  3. Email to the warehouse
  4. Manual inventory check
  5. Purchasing spreadsheet
  6. Manual supplier comparison
  7. Email to the buyer
  8. Supplier platform
  9. Confirmation email
  10. Manual status update
  • Many systems
  • Manual retyping
  • No single status
  • Lots of off-system chatter

Target — TO-BE

Buying components with INVO

One flow, one status, one set of numbers.

  1. Production scheduleThe plan is the starting point, not a spreadsheet.
  2. Automatic requirementINVO calculates needs from the schedule, BOMs and inventory.
  3. Purchasing recommendationThe system shows what to order and when.
  4. Supplier selectionThe buyer decides with the data in one place.
  5. ApprovalA workflow that follows your own rules.
  6. OrderThe PO goes to the supplier.
  7. Current status in INVOThe whole organization sees the same information.
  • Less manual work
  • Fewer systems
  • One data flow
  • Clear ownership
  • More automation

We do not move the existing chaos into a new system. First we improve the process, then we build it into INVO.

From analysis to rollout

The process map does not go in a drawer.

The agreed TO-BE process becomes the shared basis for the whole implementation — configuration, automations, test scenarios and training all come from it.

TO-BE process

How the organization is meant to work after go-live

One agreed document that five downstream work streams read from, so configuration and training can never describe different processes.

  1. INVO configuration

    Roles, workflows, permissions and settings all follow the agreed process.

  2. Automations and integrations

    We decide which actions a person performs and which can run on their own.

  3. Testing

    We check the whole process against real operating scenarios.

  4. Documentation

    The target process becomes the organization’s reference point.

  5. Training

    Every role learns the processes it will run once INVO is live.

Training & adoption

We don’t teach people where to click. We teach them how to work.

The same process we learned, simplified and built into INVO is what we use to train your team.

So the user is not learning abstract system features. They are learning to do their own daily job in the new system.

See how we train teams

Role: Buyer

Process: fulfilling a purchase requirement

  1. 01Review the requirement
  2. 02Check the system recommendation
  3. 03Compare suppliers
  4. 04Select the supplier
  5. 05Prepare the order
  6. 06Send it for approval
  7. 07Track the confirmation
Process complete7 / 7 steps

Discovery & Process Mapping

From how you work today to how your organization can work with INVO.

We can learn your processes in workshops or watch them directly in recordings of real work. We then compare them against the INVO Process Library, design the target processes, and use those as the basis for both the system rollout and the team training.

  1. 01

    We learn

    How do you really work?

    • Process workshops
    • Recordings of real work
  2. 02

    We map

    The AS-IS picture.

    • Processes
    • Roles
    • Data
    • Systems
    • Decisions
    • Exceptions
  3. 03

    We compare

    Your processes against the INVO Process Library.

  4. 04

    We design

    The TO-BE model.

    • Keep
    • Simplify
    • Adapt
  5. 05

    We roll out

    INVO, configured for the agreed processes.

    • Configuration
    • Automations
    • Integrations
    • Testing
  6. 06

    We train

    Your team, on the very processes designed during the rollout.

We do not map processes to produce a diagram. We map them to design the way your organization will work after go-live.

Ready to map your operation?

Let’s walk through your real production flow.

Book a workshop and we will go through it end to end — from contract to delivery lot — and show you where the process can be simplified.

Book a process workshopBook a demo

Continue exploring implementation

Data migrationData ready for day one.Training & adoptionRole-based training and support.Implementation processTen stages to go-live.