How to Build a Step-by-Step Guide for Any Enterprise App in 10 Minutes

Most enterprise teams assume building in-app guidance is a big project. Something that requires developer involvement, weeks of planning, a vendor onboarding cycle, and a budget conversation with finance.

It doesn't.

I've built walkthroughs for SAP IS-U, Oracle CC&B, Maximo, ServiceNow, and a dozen other enterprise apps. The longest one took 20 minutes. Most take under 10.

Here's the exact process.

What you need before you start

• Access to the web application you want to guide (logged in, on the right screen)
• The WalkAbout Chrome extension installed
• A WalkAbout account (free tier works)

That's it. No API keys. No code changes. No IT ticket.

The 10-minute walkthrough: step by step

Minute 0–1: Pick your workflow

Don't start with something complex. Pick a single, well-defined process that you already know how to do. Good first candidates:

• A form submission your team does daily
• An approval workflow that new hires struggle with
• A multi-step configuration that generates support tickets
• An onboarding task for a new system

The rule: if you can do it yourself in under 5 minutes, you can guide it in under 10.

Minute 1–3: Start recording

Open the target application in Chrome. Click the WalkAbout extension icon and hit New Walkthrough. Give it a name — something your users would search for, like "Create a new service order" or "Submit a meter reading."

Now, simply perform the task. Click the first field you'd click. WalkAbout captures it.

Each time you interact with an element — clicking a button, filling a field, selecting a dropdown — the extension records it as a step. You'll see a small overlay confirming each capture.

You're not writing documentation. You're just doing the work.

Minute 3–7: Add context to each step

After you've walked through the process, switch to the WalkAbout editor. You'll see every step laid out in sequence, each one anchored to the exact element you interacted with.

Now add the context that makes this useful:

• Step title: What the user is doing. "Select the customer's rate class."
• Description: Why it matters or what to watch for. "Choose 'Residential' for standard accounts. Commercial accounts require manager approval."
• Callout position: Adjust where the tooltip appears so it doesn't block the field.

This is where your domain expertise becomes the product. You're not just saying "click here" — you're encoding the knowledge that lives in your head and nowhere else. The stuff that isn't in the SOP binder. The stuff a new hire would only learn by sitting next to a veteran for three months.

Minute 7–9: Set targeting and triggers

Decide who sees this guide and when:

• URL match: The guide appears only on the right page (e.g., /service-orders/new)
• User segment: All users, or just a specific role or department
• Trigger: Automatic on page load, or manual launch from the help menu

For your first guide, keep it simple: show it to everyone on the target page, triggered automatically.

Minute 9–10: Preview and publish

Hit Preview to walk through the guide yourself. Check that:

• Every step highlights the correct element
• The callouts don't overlap important fields
• The descriptions make sense to someone who hasn't done this before

When it looks right, hit Publish. The guide is now live for every user who visits that page.

No deployment. No release cycle. No waiting for the next sprint.

What you've actually built

In 10 minutes, you've created something that would traditionally require:

Traditional approach	Time	Cost
Write an SOP document	2–4 hours	Internal staff time
Add screenshots and formatting	1–2 hours	Internal staff time
Route for review and approval	3–5 days	Calendar time
Distribute to users	1 day + follow-up	Email + SharePoint
Total	1–2 weeks	$500–$2,000 in labor

Your walkthrough took 10 minutes. It lives inside the app. It updates in seconds when the UI changes. And it's available to every user, every time — not buried in a folder they'll never open.

Tips for guides that actually get used

Keep steps short. One action per step. "Click the dropdown" is one step. "Select Residential" is the next. Don't combine them.

Write for the anxious new hire. They don't know the jargon yet. They're afraid of breaking something. Your descriptions should reassure them: "This field auto-saves — you can change it later."

Use branching for decision points. If step 4 depends on whether the account is residential or commercial, use an ActionBot instead of a linear walkthrough. WalkAbout's branching logic handles this without duplicating guides.

Name guides like search queries. Users will look for "how to submit a meter reading," not "MR-2024-Process-Guide-v3-FINAL." Use natural language.

Test with a real user. Watch someone who doesn't know the process follow your guide. Where they hesitate is where your description needs work. Five minutes of observation saves hours of revision.

The compounding effect

Your first guide takes 10 minutes. Your tenth takes 5 — because you've built the muscle memory and you know which details matter.

By the time you've built 20 guides covering your core workflows, you've effectively created a self-serve training system that:

• Onboards new hires in days instead of weeks
• Survives every system update (just update the affected steps)
• Reduces support tickets for routine processes
• Provides compliance-ready proof that users followed the correct procedure

And the whole library took less time than writing a single traditional training manual.

Start now

Pick the one workflow that generates the most "how do I do this?" messages on your team. Open the app. Start recording.

Ten minutes from now, you'll have a guide that answers that question forever.

Build your first guide free →

— James Osborne, CEO & Founder, APILake LLC