Fictional organization · synthetic data for demonstration

From the first interview
to the boardroom.

Riverbend Community Credit Union is a $612 million institution we invented to show what our Business Process Analysis tool does. Follow it from a conversation with the CEO to mapped processes, verified technology dependencies, a modernized wire process and a board dashboard that says, in plain language, where the business is exposed and what to do about it.

8
lines of business ranked
20 · 105
processes · steps mapped
52
systems and shared services linked
22
risks turned into board language
Narrated walkthrough · real screens from the tool
How It Works

Five stages. One connected picture.

Every answer lands in one secure engagement record, so a statement made in an interview can be traced all the way to the risk the board sees.

  1. STAGE 1

    Discover

    The top executive names the lines of business and ranks them by how fast failure would hurt.

  2. STAGE 2

    Map

    Each leader walks us through people, process and technology, step by step, into swim lanes.

  3. STAGE 3

    Connect

    Systems and shared services are linked, so a weakness in one place shows everywhere it lands.

  4. STAGE 4

    Verify

    Real network traffic is compared with what people told us, exposing what nobody mentioned.

  5. STAGE 5

    Decide

    Findings become plain-language risks, recovery checks and clear asks for the board.

Stage 1 · Discover

Start where the business starts: with what can't fail.

In a 60-minute session, Riverbend's CEO named eight lines of business and ranked them by the damage of a stoppage. Member Accounts and Payments came out on top: payroll deposits and wires can't wait more than a few hours.

  • Criticality and "down before harm" captured in the executive's own words
  • Risk appetite recorded up front, so every finding is judged against it
  • Gaps and conflicts become owned open items, never guesses
Stage 1 screen: Riverbend's executive interview beside eight lines of business ranked by criticality, with down-before-harm times.
Lines of business, most critical firstThe executive interview and the ranked list sit side by side.
Stage 2 · Map

How a wire really gets sent.

The Payments manager described the process step by step. The tool turned it into a swim lane and flagged what a policy manual never shows: everything runs through one trained person on one computer.

Swim lane: Send an outgoing wire transfer (Riverbend, fictional) Seven steps across five roles. Step 2, entering the wire, is a single point of failure: one trained person and one computer at headquarters. Step 4 is a dual-control decision whose backup approver token has not been used in nine months. PRC-02.01 · SEND AN OUTGOING WIRE TRANSFER · 15–40 PER DAY Teller / Member Service Rep Wire & ACH Operations Specialist Payments Operations Manager Corporate credit union (outside) Staff Accountant Take request; verify member by callback Core banking · phone system 1 Enter wire in corporate CU portal Wire portal · ONE release PC 2 Screen against OFAC & fraud flags AML monitoring 3 Second approval (dual control) Wire portal · same PC 4 Debit member account Core banking 5 Settle & confirm Wire network 6 Reconcile wires to general ledger GL · core banking 7 Step 2 · Single point of failure: one trained person, one computer at headquarters, no tested alternate Step 4 · Backup approver token has not been used in nine months

No process left half-asked.

A prescriptive People, Process and Technology question set runs for every process. A coverage meter shows what's still missing, and "I don't know yet" becomes an open item with an owner instead of a blank.

  • Roles, systems, decisions and handoffs captured on the spot
  • Single points of failure and manual workarounds recorded per step
  • Swim lanes export to PDF, Lucidchart and Mermaid
Stage 2 screen: each Riverbend line of business with its leader interviewed, process count and a coverage meter.
Interview coverage by line of businessEvery leader, every process, and how much of the question set is answered.
Stages 3 & 4 · Connect and Verify

Trust what people say. Then check it.

The technology map shows which systems each process depends on and what information moves between them. Then we import network flow records and compare: documented links that never appear, and real conversations nobody mentioned.

Technology map for Payments and Funds Transfer: wire portal, ACH module, core banking, general ledger and AML monitoring with typed links.
Technology map · Payments & Funds TransferSystems laid out automatically, with how they exchange information and what each one needs to run.
Network evidence screen comparing the ACH process interviews with observed traffic; one server-to-file-server conversation is marked Not in the interviews.
Network evidence vs. the interviewsFor ACH, flow records show the payments server talking to a file server that no one described.
24
systems, and all 8 lines of business, sit on one HQ internet line
5
lines of business depend on one external DNS provider
10
network conversations not in any interview (ACH)
18
open items, each with an owner
Working With AI

AI does the heavy lifting. People make the calls.

AI is built into the tool where it saves real hours, and every output is reviewed and approved by a Simplex consultant before a client sees it.

Live transcription

With recorded consent, interviews are transcribed as people talk, so consultants listen instead of typing. Off by default per engagement.

Analysis, drafted by AI

From the engagement record, AI prepares interview guides, reconciles conflicting answers and proposes indicators and risk scenarios for the team to review.

Board-language risks

Technical findings are rewritten as "if this happens, here's what the business loses," with jargon blocked from the board view.

A consultant signs off

Nothing AI drafts reaches a client unreviewed. Every statement on the board view carries a Simplex consultant's approval.

Modernize the Process

Fix the process, then automate it.

Because we mapped how wires really move, the redesign targets the actual weak points instead of buying another tool.

Today, as described in the interviews

  1. Mortgage funding wires are requested by emailNo documented callback before funds move
  2. One trained operator enters every wireIf he is out, wires stop or go out untrained
  3. Release only from one headquarters computerThe recovery branch has no way to send wires
  4. Backup approver token sits unused for nine monthsNobody knows whether it still works
  5. The ACH server has never been restored from backupAbout 36 hours to rebuild against a same-day need

Future state we would design with Riverbend

  1. One secure wire request form for branches and closersCallback to the number on file is required and logged before the wire can proceed
  2. A second operator cross-trained and rotated monthlyCoverage proven, not assumed
  3. A second release station at the Lakeside recovery siteTested quarterly alongside the phone-in procedure
  4. Backup approval exercised on a scheduleResults recorded as evidence for examiners
  5. Automated sanctions screening and daily reconciliationExceptions routed to a person; everything else flows

Future-state items are Simplex recommendations for the fictional Riverbend case, shown to illustrate the method.

Stage 5 · Decide

The board view.

Ten minutes, five questions: which business functions are at risk, are we inside our appetite, can we recover in time, what would cause it, and what do you need from us. No hostnames, no vulnerability counts, just consequences and decisions. Select a function to see why.

Fictional organization · Synthetic data · Shown to illustrate the method

Riverbend Community Credit Union · Cyber & Resilience Risk

Baseline assessment · November 2026 · Prepared by Simplex for the Board of Directors
Functions rated High
2 of 8
Payments and Digital Banking
Outside risk appetite
3 of 8
business functions
Recovery never tested
3 of 8
including Payments
The one thing to know
If headquarters loses its single internet line, every branch, card servicing and wires stop together. The CEO believes a second line is funded; IT says it was cut.

Business function risk map

Ordered by criticality HighModerateLow► Baseline (first assessment)

Can we recover in time?

hours · 0 to 5 days
Time the business can tolerateRecovery shown in a testTook longer than toleratedNever tested

Services many functions rely on

business functions affected
Headquarters internet line8 of 8

One line, no second path. Branches reach the core through it. Second line's funding is disputed.

Headquarters server room power8 of 8

About 40 minutes of battery; the generator is switched on by hand.

Internet name service (website, online banking, email)5 of 8

One provider, one shared login without a second factor. Never assessed.

Network administrator accounts8 of 8

Six everyday accounts, including the IT provider's, also open the backup system.

Top risks

owner and treatment for each
RatingWhat could happenOwnerTreatment

What we need from the board

Settle and fund the second internet lineResolve the conflict between the CEO and IT and fund a diverse path this cycle.
Approve a wire resilience programSecond trained operator, a Lakeside release station and a tested phone-in procedure within 90 days.
Require a second sign-in factor everywhere money or names moveCard portal, internet name provider and all administrator accounts.
Direct overdue vendor reviewsInternet name provider and mortgage subservicer, reported back next quarter.

Third parties critical functions depend on

Core banking processorReviewed; one exception
Card processorReviewed; sign-in gap not raised
Online & mobile bankingReviewed
Corporate credit union (wires, ACH)Reviewed
Managed IT providerOpen: audit report requested
Internet name providerNever assessed
Mortgage subservicerOverdue since 2024

Ratings combine likelihood and impact (High 15+, Moderate 9–14, Low 8 or less on a 25-point scale). Every rating shows a word and a shape, never colour alone. Trend shows "Baseline" because this is the first assessment.

Resilience

What changes after the board meeting.

The dashboard isn't the end. Each ask becomes a tracked action with an owner, and the same engagement is reassessed so trends show Improving or Worsening against this baseline. Recovery claims move from "stated" to "demonstrated" as tests are run, and VIRTEx exercises can rehearse the scenarios that matter most, like losing headquarters on a payroll day.

  • Stated vs. demonstrated recovery for every function
  • Shared-service failures traced through every process they touch
  • Indicators can feed from Splunk for ongoing measurement
Open items screen listing missing facts, assumptions to confirm and conflicts, each with an owner and a Resolve button.
Open items with ownersUnknowns, conflicts and telemetry gaps stay visible until someone resolves them.

See your own organization this way.

A discovery engagement takes your leaders' knowledge and turns it into a map, a modernization plan and a board-ready view of risk.

Riverbend Community Credit Union, its people, vendors and incidents are invented. Any resemblance to a real organization is coincidental.