How the work actually works: enlotic case studies

Explore a selection of work that shows the range of what Enlotic does: untangling large, multi-team projects before they buckle under their own size, designing around behavior so the long-term smart choice becomes the easy one, and pulling a business’s know-how out of one person’s head and into something the whole organization can use. Different industries, different problems, same approach underneath.

Here some sort of testimonial.

Speaker Name

Background
As LTS expanded its calibration services to include non-nuclear density gauges, the company found that its equipment repair and calibration procedures existed almost entirely as tacit knowledge — held by a small number of senior technicians who had learned gauge-specific calibration steps (for lines like the 3430+/3440+, MC-3, and 3500 Xplorer) through years of hands-on repair work rather than written reference.

The Problem

• No standardized calibration checklist per gauge model
• New hires shadowed veteran techs for weeks before being trusted on customer equipment
• Institutional knowledge was at risk with any single technician’s departure
• Parts-ordering knowledge (which replacement part maps to which failure symptom) lived in one person’s memory

The Intervention
LTS undertook a documentation initiative to:

1. Interview senior technicians and capture step-by-step calibration procedures for each major gauge family
2. Convert those interviews into written SOPs, organized by product category (mirroring the site’s own category structure — density & Rice testing, gyratory parts, sieve/gradation equipment, etc.)
3. Compile an employee handbook covering safety procedures, customer-facing service standards, and equipment-specific troubleshooting trees
4. Pilot the handbook with a new-hire technician to validate clarity before rollout

Outcome (placeholder)

• New technician ramp-up time reportedly cut from ~6 weeks to ~2 weeks
• Reduced calibration errors during the initial post-documentation quarter
• Created a living document that’s updated as new gauge models are added to the shop’s catalog

The £18,000 Weekend: How Enlotic designs a retention strategy around a behavioral risk

Firm: Enlotic — Knowledge Management Consulting
Lead: Mark Gottschalk, Founding Consultant
Client: A UK challenger investment platform (anonymized)
Engagement type: Strategic knowledge management — behavioral design, learning strategy, and instructional design
Capabilities shown: Strategic Vision, Project Management, Content Creation
Status: Proposal delivered and well received; the client later shelved the initiative during an internal budget reprioritization, unrelated to the strategy itself.

What Enlotic does

Enlotic is a knowledge management firm. We help organizations capture what they know, decide what to do with it, and put it in front of the right person at the right moment. That umbrella is wide — it includes internal documentation and org strategy — but this piece zooms in on one application, because the best way to show how we think is to watch us solve a specific, thorny problem.

This engagement is a representative example. It shows the granular level of detail we work at, and how our three core sub-capabilities — strategic vision, project management, and content creation — combine into a single, deployable solution.

The problem

Our client offered Junior ISAs — tax-free investment accounts a parent opens for a child. The product had a structural flaw that no marketing budget could fix: the 18-year-old cliff.

UK law says that the day the child turns 18, the account converts to an adult ISA and they gain absolute, unrestricted access to every pound. Years of disciplined parental saving can legally evaporate in one impulsive weekend. The platform can’t lock the funds — and parents know it. That fear was suppressing sign-ups before the product ever had a chance to prove itself.

This is, at its core, a knowledge problem. The right information existed — what the money could become, what a withdrawal really costs — but it was nowhere near the moment a frightened 18-year-old reached for the “Withdraw All” button. Our job was to close that gap without breaking the law.

The strategic insight

You can’t lock the door. So we designed a way to make the door harder to open and the room more rewarding to stay in.

We proposed a layered intervention built on behavioral economics, ordered from highest to lowest impact so the client could adopt all of it or start with one piece:

• Choice architecture. Replace a single “Withdraw All” button with a menu: keep the tax-free wrapper, set up a modest monthly allowance, or withdraw a specific sum for a real goal. The most beneficial path becomes the obvious one.
• Cooling-off friction. A large withdrawal triggers a mandatory 3-to-5-day reflection period — long enough to interrupt an impulse, short enough to stay legal. During the wait, the user sees what that same money could be worth in a decade.
• A profit moment instead of a loss. At 18, offer a one-click transfer from the matured account into a pension. Move £2,880 in, and the government adds £720 in tax relief — turning £2,880 into £3,600 instantly. That feels better than a frivolous purchase, because it reframes “leaving money alone” as winning something.
• Early ownership. Use the legal window at 16–17 — when a teen can view and manage but not withdraw — to give them view-only access and a “practice” portfolio. Watching the balance grow and dip for two years removes the lottery-win shock at 18.

The part most consultants skip: regulatory grounding

Friction is dangerous territory in UK finance. Add too much and you’ve broken HMRC’s rule that an 18-year-old has an absolute right to their money. So we did the homework that makes a strategy usable rather than just clever.

We mapped the entire intervention against the FCA’s Consumer Duty, which since 2023 has required firms to prevent “foreseeable harm.” Letting a teenager accidentally liquidate a high-performing account into a 0%-interest account, with no explanation, is arguably exactly that harm. Helpful friction isn’t a barrier — it’s the firm meeting its duty.

The line we drew, and documented for the client’s risk and compliance teams, was the difference between a nudge (legal: making the best path the prominent one) and sludge (non-compliant: hiding the exit, demanding a mailed letter, imposing an absurd 30-day delay). Our blueprints didn’t just propose features — they gave the compliance team the language to approve them.

How an Enlotic engagement executes

A strategy that sits in a slide deck changes nothing. We design for the whole arc.

• Strategic vision. We find the high-risk “leakage” points where value quietly leaves a platform, and we design the cognitive-friction solutions that stop it — backed by research the client’s own internal teams can stand behind.
• Content creation. We don’t ask a client’s design team to suddenly become financial educators. We build the just-in-time content library for them: 30-second videos and interactive tools that fire at the exact moment of decision, matched to the client’s brand so the education feels like a premium feature, not a bank lecture. The hard part is pedagogical — making a concept like a pension tax bonus land with an 18-year-old in under thirty seconds. That’s instructional design, and it’s what we do.
• Project management. We act as specialized PMs so these features don’t die in a backlog — coordinating the cross-functional flow between engineering, design, and compliance until the thing actually ships.

Why this is a knowledge management problem

Strip away the fintech specifics and the shape is universal: an organization holds knowledge that, delivered at the wrong time, is worthless — and delivered at the right time, changes behavior and protects value. Finding those moments, deciding what the person needs to know, designing how they learn it, and managing it into production is the core of what Enlotic does.

The same method applies whether the “leak” is customer assets, undocumented institutional expertise walking out the door, or a training program that teaches the wrong thing at the wrong time. We find the problem, design the solution, ground it in the rules you operate under, and manage the execution.

The client’s initiative didn’t launch — the funding behind it was pulled before implementation began, a decision made above the product team and unrelated to the proposal’s reception. The strategy stands as designed: a worked example of the capability, not a claim of deployed results.

Two Quarters, 140 Deliverables: How Enlotic builds the system that makes a complex program deliverable at scale

Firm: Enlotic — Knowledge Management Consulting
Lead: Mark Gottschalk, Founding Consultant
Client: A national credit union (anonymized)
Engagement type: Strategic knowledge management — project systems, cross-functional coordination, and delivery infrastructure
Capabilities shown: Strategic Vision, Project Management, Content Creation

What Enlotic does

Enlotic is a knowledge management firm. Most of our work is visible in the artifact it produces — a training module, a behavioral strategy, a piece of content someone reads or clicks through. This piece is different. It’s about the infrastructure underneath that kind of work: the system that has to exist before 50 people across a dozen roles can reliably ship 140 things without losing quality, missing a deadline, or losing track of who owns what.

That infrastructure is invisible when it works. This is the story of building it.

The problem

A learning and development department of 30+ people needed to rewrite more than 140 pieces of curriculum within two quarters, spread across up to seven concurrent, high-visibility projects. The work touched subject matter experts, developers, HR partners, and senior business leaders — each with their own priorities, their own calendar, and their own definition of “done.”

At that scale, the risk isn’t any single deliverable failing. It’s the system around the deliverables failing first — inconsistent review standards, unclear ownership, status that lives in someone’s head instead of somewhere visible, and a portfolio that quietly drifts off schedule because no one can see the whole board at once. A department can have excellent individual contributors and still miss its numbers, because the coordination layer was never built.

The systems insight

You can’t manage 140 deliverables one at a time. You manage the process that produces them.

We standardized the department’s project workflows in Jira and Asana, replacing ad hoc tracking with a single, repeatable pipeline every piece of curriculum moved through:

• A consistent review gate. Every deliverable passed through the same stages — alpha draft, structured SME and peer review, beta, final — so quality didn’t depend on which team happened to build it.
• Visible ownership. Every workstream had a named owner and a milestone tracker that made status legible to anyone who looked, not just the person running it.
• Standing documentation. Timelines, budgets, and status reports were kept current as a matter of process, not reconstructed under pressure before a leadership update.

This is the same move as any Enlotic engagement — find where a system is invisible, undocumented, or living in one person’s judgment, and make it explicit enough that other people can rely on it.

Cross-functional leadership

A system only works if the people running through it trust it, and trust has to be built role by role. We served as the primary liaison between the learning team, HR partners, and C-suite business leaders — translating strategic priorities into project plans the delivery team could actually execute against, and translating delivery-team reality back into terms leadership could act on.

That two-way translation is where most large programs actually break. Strategy gets set without knowing what’s deliverable; delivery teams execute without knowing why a priority shifted. Sitting in the middle of that, with standing documentation both sides could see, closed the gap.

The result

Across two quarters, the department delivered more than 140 learning assets through this system — on time and to a guaranteed quality standard — while running up to seven concurrent high-visibility projects and coordinating a working group of 50+ contributors. The standardized workflow also reduced development cycle times departmentwide, a change that outlasted any single project because it changed how the team worked, not just what it shipped.

Why this is a knowledge management problem

Strip away the credit union specifics and the shape is familiar: an organization’s ability to execute was limited not by talent or effort, but by the fact that process knowledge — who owns what, what “ready for review” means, where a project actually stands — lived nowhere anyone could see it. Making that knowledge explicit, standardized, and visible is what let the department operate at a scale it couldn’t sustain informally.

This is one worked example. The capability behind it — building the system that makes complex work deliverable at scale — is the offering.

A couple of things worth flagging before this goes anywhere:

1. The specific numbers (140+ assets, 50+ contributors, up to 7 concurrent projects, department of 30+, two quarters) came from your resume language in an earlier chat — worth double-checking them against your own records before this goes public, since I’m reconstructing from what you’d written elsewhere, not from a document you gave me for this piece specifically.
2. “Reduced development cycle times” was in your resume without a number attached. If you have an actual figure (e.g., “-20%”), it’d strengthen this section a lot — right now it’s a real claim but a soft one.

Case Study 4

Case study 4 info.

Case Study 5

Case study 5 info.