Product — by Polaris Closed Beta

FriktionSee where work gets stuck.

Most operational drag is scattered across waiting, handoffs, rework and small workarounds. Friktion brings those traces together, shows what they cost, and gives you a practical order for fixing them. Then it returns to the same evidence to see what changed.

A Polaris product, created for the kind of operational work we do with clients.

Where the time goesIllustrative
ActiveWaitingApproval
Elapsed time split into active work and waiting, one bar per case. Invented shapes, not client data.

Friktion at a glance.

Status
Closed Beta.
Built for
Small and medium-sized organisations that want evidence before changing how work gets done.
Works with
Process documents, operational exports, time logs, interviews, email and chat.
Produces
A workflow map, nine-part friction profile, prioritised roadmap, governed blueprints and a follow-up measurement.
Evidence
Every figure is labelled measured, documented, stated or unverified, with its coverage kept visible.
Role of AI
Models help read and organise source material. Versioned code produces the official figures, and people review the decisions.

01 — How it works

A clear path from evidence to a better way of working.

We begin with the traces a workflow already leaves behind. From there, Friktion helps a team understand the drag, choose a response, shape the work and return to the evidence after the change.

  1. Measure

    Follow the work as it happens

    Reconstruct the workflow from records, documents and the people who know it.

    Stage 01 · Clarity
  2. Decide

    Choose the right place to intervene

    Start with the structure: remove a step, simplify it, or make ownership clear.

    Stage 02 · Architecture
  3. Build

    Turn the decision into something usable

    Create the workflow, specification, checklist or automation the team can put into practice.

    Stage 03 · Intelligence
  4. Measure again

    Return to the evidence

    Use the same yardstick to understand what moved and what still needs attention.

    Stage 04 · Partnership
Think of it as…

A Friction Audit you can revisit, compare and act on. See the Polaris model

02 — What goes in, what comes out

The traces your work already leaves, turned into a plan.

You provide

What the work leaves behind

  • SOPs, checklists, manuals and role descriptions
  • Exports from ticketing, CRM, ERP, order and other workflow systems
  • Time logs, when the team has them
  • Interviews, email and chat that fill in what the records cannot show
You get

A view the team can use

  • A map of the documented workflow beside the path cases actually followed
  • A nine-part friction profile, with the basis and coverage of every figure
  • Delay and effort, with any assumptions printed alongside the numbers
  • A Now, Next, Later roadmap, including anything blocked and the reason why
  • A governed blueprint the team, Polaris or another partner can implement
  • A follow-up measurement using the same protocol

03 — The profile

A fuller picture of the workflow.

Friktion looks at a named flow of work from its trigger to its outcome—quote to order, for example, or new-hire onboarding. Nine dimensions show where the drag appears and how it behaves.

The dimensions stay visible; they are never flattened into one score.

  1. 01

    Flow

    Separates active work from the time cases spend waiting.

  2. 02

    Handoffs

    Tracks where work changes hands and where something gets lost along the way.

  3. 03

    Rework

    Finds cases that return to an earlier step, reopen or need correction.

  4. 04

    Duplication

    Surfaces work or information that the team creates more than once.

  5. 05

    Manual transfer

    Shows where people re-key or carry information between systems.

  6. 06

    Gating

    Looks at the delay created by approvals and whether they alter the outcome.

  7. 07

    Information

    Identifies work that stops while someone searches or waits for missing input.

  8. 08

    Exceptions

    Measures cases that leave the usual path and the extra cost they carry.

  9. 09

    Variation

    Compares the paths cases take with each other and with the documented process.

When the evidence cannot support a dimension, the profile says “not measured” and explains the gap.

04 — Why it's different

You can see how every conclusion was reached.

Evidence

Findings you can trace

Open a finding and follow it back to the verified quote, cell or data row that supports it. Anything that cannot be checked stays visible as unverified and does not enter the totals.

Calculation

Figures with a clear lineage

Versioned code calculates the published numbers from stored observations. Models help read the material; they do not calculate, adjust or round the result.

Basis

The source travels with the number

Measured, documented, stated and unverified evidence remain distinct, so a confident-looking total cannot hide a weak foundation.

Order

Fix the work before adding technology

Friktion looks for a step that can be removed, merged or clarified before it considers automation or AI.

Before and after

Agree on the test before the build

The team records what it expects to move, how it will be measured and when the follow-up starts before the change goes live.

Review

Judgement stays with people

A reviewer resolves uncertain evidence and accepts the workflow maps, recommendations and blueprints that move forward.

  • Frozen baselines
  • Model-agnostic
  • Time logs supported
  • Built for SMEs

05 — Evidence

Every figure comes with its own paper trail.

Friktion keeps the written process, the operational record and people's account of the work separate. A model can propose what a source means, but code still has to find the supporting quote or cell. The gap between the process on paper and the process in practice often reveals the most.

  1. Measured

    Code derives the figure from timestamps, status changes, owners, outcomes or time logs.

  2. Documented

    An SOP, checklist or other source describes how the work is meant to run, and the quoted text has been verified.

  3. Stated

    A person describes the work in an interview, email or message. A headline uses it only when another independent source agrees.

  4. Unverified

    The source could not be checked. It remains visible for review but stays out of the figures.

06 — Deciding what to change

Start with the change that earns its place.

A recommendation begins with a named friction event and the evidence behind it. Friktion works up from small structural changes to integration, automation and AI, stopping as soon as there is a credible answer.

  1. Eliminate a stepDays
  2. Merge or parallelise stepsDays to weeks
  3. Standardise: template, checklist, definition of doneDays
  4. Clarify ownership and decision rightsDays
  5. Change a policy or thresholdDays
  6. Train and documentDays
  7. Fix the data at sourceWeeks
  8. Integrate systemsWeeks to months
  9. Automate a rule-based stepWeeks
  10. AI assist: draft, triage, summarise, extractWeeks
  11. AI agent: multi-stepMonths

07 — Did it work?

Improvement should survive a second look.

Before a change goes live, the team records what it expects to move and how the follow-up will be run. The result then carries the strongest claim the evidence can support. For most SME engagements, that will be one of the first two levels.

Claim levels, what each one lets us say, and what it requires
LevelWhat we can sayWhat it requires
T0 · DescriptiveIn this period, on these sources, the workflow waited this long.A frozen protocol, with coverage and basis reported.
T1 · AssociativeThe measure moved. Other changes are not separated out.Two or more cycles on an identical protocol.
T2 · ControlledIt moved more than comparable workflows we left alone.Pre-registration, plus unchanged control workflows or a staggered rollout.
T3 · CausalThe intervention caused the change.Randomised or staggered assignment, pre-registration and replication.

The expected movement is written down before the change goes live. A cycle with no movement, or movement the wrong way, is reported in full. No part of the measurement fee depends on measured improvement.

08 — Honest by design

Clear about the limits of the evidence.

Scope

The workflow stays in focus

Findings remain attached to a named flow of work and the evidence behind it. Friktion does not collapse an organisation into a single score.

Baseline

A starting point you can return to

The first cycle establishes a repeatable baseline. Later cycles show whether the measured friction moved; they do not turn assumptions into a promise of savings.

Coverage

Documents are only one view

A written process shows how work is meant to run. Friktion marks the limits of that evidence until records or independent accounts show what happens in practice.

Purpose

Technology has to earn its place

The goal is to improve the work. Sometimes that calls for automation or AI; often the better answer is to remove a step, clarify a decision or fix the source data.

10 — FAQ

Questions we expect.

What does “friction” mean here?

It is the avoidable waiting, rework, duplication and effort between the start of a workflow and its outcome. Friktion compares a workflow with its own demonstrated best and connects every finding to a possible intervention.

Will it tell us how much we will save?

It will show the delay and effort visible in the evidence, along with scenarios for recoverable time. Those scenarios are assumptions, not promises, and every figure says whether it was measured, documented or stated.

What data does it need?

Friktion can work with process documents, exports from systems such as ticketing, CRM, ERP or order tools, time logs, and interviews or messages that explain how the work really happens. It can begin with documents alone, but the profile will make that more limited basis clear.

Is this an AI tool?

AI helps Friktion read and organise the source material, but it does not produce the official numbers or make the final decision. The method starts with the workflow itself and considers AI only where it is a better answer than removing or simplifying a step.

Who is it for?

Friktion is being built for small and medium-sized organisations that know a workflow is harder than it should be and want evidence before deciding what to change.

Next step

Bring us a workflow that feels harder than it should.

We will help you work out where the friction sits and whether Friktion is the right way to investigate it.

Start a Friktion conversation