Skip to content
AI Process Engineer

How the Process Engineer works

It combines observed work, process analysis, control context and a Black Belt–style review in one governed workflow.

A question leads to an evidence brief that a reviewer examines.

The evidence it starts from

Findings come from a synthetic sample of 10 applications.

The question

“New member accounts take too long.”

Where the time goes
  • The longest wait sits at joint-owner approval by email: 4.5 hours on average, across 3 applications.
  • Account creation came about 75 minutes after OFAC screening on average (4 applications), against 15 to 30 minutes for the other hand-offs on that route.
  • The same kind of application was handled four different ways across 10 applications.
Patterns for review
  • In 4 of 10 applications, ID was verified by hand on a paper form.
  • In 3, joint-owner approval was handled by email, outside the system of record.
  • Three steps are flagged as high-tier automation candidates.
Controls
  • The CIP check was logged in 6 of 10 applications.
  • The other 4 took the paper ID route, which matched no control in the library, so your expert confirms whether it is a control point.

Follow the paper-form route. Four of the ten synthetic applications took this path. Find the manual ID check and see where the routes rejoin.

MEMBER ONBOARDINGBranch systemMember service repCompliance systemJoint ownerBranch managerCard servicesReceiveapplicationReviewapplicationVerify IDmanuallyRun BSA/AMLCIP checkOFACscreeningEmail jointownerReceiveapprovalCreateaccountManagerapprovesOrderdebit card4 of 10 · paper form4.5 h avg wait1
Simplified from the BPMN 2.0 diagram TruWyn generated for this synthetic sample; lane names shown by role. The paper-form route was planted in the synthetic data to illustrate the concept.View full generated diagram

Member onboarding, simplified BPMNScroll or pinch to move around

Selected step
Run BSA/AML CIP Check
1Suggested control
Customer Identification Program (CIP)
Reviewer’s question
Where in this case can we see evidence that the identity check took place?
Regulatory reference
31 CFR 1020.220, customer identification programs

Five steps to a decision your people sign

The review follows Lean Six Sigma: ask, charter, brief, test, decide.

Observed work
Step 1 of 5 · Ask

Ask a question

What TruWyn does

Five plain questions: the problem, why it matters now, how you will know it is fixed, what is in scope, and what you will decide.

What you hold

Your question, in your own words

  1. What is the problem?
  2. Why does it matter now?
  3. How will you know it is fixed?
  4. What is included, and what is not?
  5. What will you decide at the end?
Step 2 of 5 · Charter

Get a project charter

What TruWyn does

Drafts a six-section Lean Six Sigma charter. Every line shows whether it came from your answer or from the evidence. A senior person signs it.

What you hold

A signed six-section charter

Business caseProblem statementGoal statementProject scopeHigh-level timelineStakeholders and team

Each line is marked:

From evidenceYour answerTo be measuredFor the team
Step 3 of 5 · Brief

Read the brief

What TruWyn does

Measures what the evidence supports and shows the charts. It also lists what it could not measure, and why.

What you hold

A brief with charts, and a list of what it could not measure and why

Step 4 of 5 · Test

Test the explanations

What TruWyn does

Sets competing explanations side by side, with the evidence for each. Your people grade them.

What you hold

Explanations your people have graded

Step 5 of 5 · Decide

Choose what to do

What TruWyn does

Lays out the improvement options and shows which controls each one touches. The result can be a pilot, no change, or more evidence.

What you hold

A recorded decision: a pilot, no change, or more evidence

How it compares

What each approach typically covers.

Each approach covers part of the work.

AskFive plain questions
CharterSigned six-section charter
BriefCharts, and what it could not measure
TestGraded explanations
DecidePilot, no change, or more evidence
Observed work
Process mining
Maps and analyses system event logs.

Covers: Brief, Test

Task mining
Maps desktop activity, friction and automation candidates.

Covers: Brief, Test

A consulting study
Experts run the method with your team. TruWyn gives them observed evidence and a record your institution keeps.

Covers: Ask to Decide

Automation and bots
After the decisionBuilds the automation once a step is chosen.

Begins after the decision

TruWyn
AskAsks five plain questions
CharterDrafts a six-section charter; a senior person signs it
BriefMeasures what the evidence supports, and lists what it could not
TestSets competing explanations beside the evidence
DecideShows which controls each option touches

Observed work

TruWyn captures how work is actually done on staff desktops, with case numbers disguised and other numbers masked before storage.

It proposes; your people decide

Every proposed change is approved by people, and their approval is recorded.

Controls in view

Improvement options show which controls each one touches.

Runs on your premises

Runs on your premises, on your hardware. Read-only toward your systems; it never writes to them.

See this on one of your processes.

Book a pilot