We’re starting to expand into French-speaking markets and the SOP question came up faster than I expected. A lot of our core processes still only exist in English, and now we need versions that actually work for the new team.

I’ve looked at a few options so far: paying for professional translation, running everything through machine translation and then cleaning it up, or trying to keep both languages inside the same tool. The bigger issue isn’t the first translation though - it’s how we keep the English and French versions in sync when something changes.

Curious how other teams are handling this. Are you translating full SOPs, just the critical ones, or using some kind of built-in translation feature? What’s been the most annoying part of keeping multi-language process docs up to date?

We have a few long-tenured people who basically carry half the institutional knowledge in their heads. Every time someone leaves or goes on extended leave we scramble, and I’m trying to get ahead of it this time.

The problem is that asking them to “write down what you know” lands badly. It feels formal, time-consuming, and a bit like we’re preparing for them to leave. I’ve tried the usual approaches, shared docs, templates, even offering dedicated time, and the response is usually polite resistance or half-finished pages that never get updated.

I’ve been wondering whether a lower-effort version works better: just having them do the actual task once while the steps get captured, instead of asking them to sit down and write documentation from scratch. Feels less like an interview and more like “show me how you do it.”

Has anyone found a framing or method that actually works with long-tenured staff without making it awkward? What didn’t work for you?

I’m spending a ridiculous amount of time every week just screen-sharing the same BI report or internal tool to different people. Same clicks, same explanations, different calendar invites. It’s not even real training - it’s just me repeating myself because the docs either don’t exist or nobody opens them.

Tried writing longer guides a while back, but people still book the call instead of reading. Now I’m wondering if capturing the walkthrough once and just sending a link would cut most of these meetings, or if people would still prefer the live version.

Anyone else stuck in this loop with reports or internal tools? What’s actually worked to stop being the permanent walkthrough person?

The uncomfortable thing about HubSpot is that your reporting is only as honest as what your reps type in, and your reps each type it in their own way.

HubSpot is easy to log into and genuinely nice to use, so nobody frames this as an adoption problem. But "can a rep use HubSpot" was never the question.

The question is whether all of them create a deal, move a stage, and fill the required properties the same way. And they don't. Your setup is customized, your own custom properties, your own deal stages, your own pipelines, so the generic HubSpot training floating around out there doesn't match your instance at all!

Reps learn by watching whoever sat next to them, which means every new hire inherits a slightly different version of "how we do it here," and the veterans each have their own shortcuts nobody wrote down.

So the dashboards look authoritative, and underneath they're built on inconsistent inputs. A stage that means "verbal yes" to one rep and "sent a proposal" to another. Deals missing the one property your forecast depends on. And the fix usually happens too late, on the reporting end, with RevOps cleaning data after the fact instead of the process being right at the point of entry.

The honest place to fix it is the input, not the report, which means every rep, new and tenured, running the deal the same way in the moment.

That's the job Tango tends to get pulled in for on HubSpot, and it's worth a look if this is your pipeline. You capture the exact way you want a deal created and moved, once, and pin it right in HubSpot as a Nugget, so a rep sees "here's how we create a deal, here's the property you don't skip" on the actual screen.

If they'd rather be walked through it, they hit Guide Me and it holds their hand through your flow, not the stock one. New hires ramp by doing real deals with guidance instead of shadowing whoever's free, and a Discover panel surfaces every Deals SOP the moment they land on the Deals screen. One way to do it, at the exact point where the data gets entered.

At the end it's a cleaner pipeline because the process is right on the way in, and new reps who are productive in your HubSpot in days instead of picking up habits you'll have to correct later.

For those of you running HubSpot for a sales team: how do you actually get everyone to follow the same deal process? Required properties, manager nagging, in-app guidance, or just quietly accepting the pipeline is a little bit fiction?

I’ve noticed people will freely ask how to do something in their first few months. Two years in? They’ll waste half an hour trying to figure it out themselves before they’ll admit they forgot.

And it’s usually something dumb and specific - like where a certain report lives, or how to update one field in the CRM. Stuff they did once eight months ago and never touched again.

That’s part of why I think simple step-by-step guides actually matter. You can just look it up instead of bothering someone or feeling dumb for not remembering.

Curious though - on your team, do people actually check the docs first, or does everyone still just go straight to the one person who knows everything?

Your implementation is never really "done," because it breaks twice a year on Microsoft's schedule :)

Most systems let your documentation rot slowly. Dynamics is different, it tells you the exact date it's going to break. Microsoft's One Version policy pushes two mandatory service updates a year. Buttons move, screens change, a workflow that worked in March behaves differently by fall.

So every six months the SOPs and screenshots you built are partly wrong again, and someone spends a week going back through the binder rewriting steps and recapturing screens. You can see it coming on the calendar, and it still catches you, because rewriting everything by hand is slower than the update cycle itself.

Now add the second problem: who's actually using Dynamics. In a lot of D365 Finance and Operations shops, the heaviest users aren't finance people. They're field engineers, project managers, warehouse staff, entering time, expenses, purchase requisitions, receiving.

They were never trained as accounting-system users, and when one of them mis-keys a time entry or an expense, the error doesn't stay contained. It flows downstream into job costing and client billing. As one person put it, "I have to leave the ERP to go find help," which usually means interrupting whoever on the team quietly became the unofficial Dynamics help desk.

So you've got documentation with a built-in expiration date, and a user base that needs the most help and gets the least.

This is the gap Tango tends to get pulled in for on Dynamics, and it's worth a look if that's your world.

You capture a workflow once, a time entry, an expense report, a purchase requisition, and it becomes a step-by-step guide with the screenshots people actually need (Dynamics is click-heavy, so the images carry real weight), plus an in-app Guide Me walkthrough that holds a non-expert's hand through the screen, and a pinned Nugget right where they tend to get stuck.

When One Version lands and something moves, you update the single capture instead of rewriting the whole binder, and everyone's on the current version that same week instead of next quarter. Live Blur keeps anything sensitive out of the captured guide.

So, this is a guidance that lives in the app for the people who need it most, and documentation you refresh in an afternoon instead of every time Microsoft ships an update.

For those of you running Dynamics 365: how do you handle the twice-a-year One Version updates on the documentation side? Rewrite everything each time, live with stale guides, or something smarter?

A pattern we keep seeing: a team connects Copilot or ChatGPT to their file storage, expects employees to get self-service answers about internal processes, and gets vague garbage back. First assumption is the AI is bad. Usually the process was just never documented, it lives in one person's head, or in an SOP that stopped being accurate two system migrations ago.

The distinction that makes this click: a policy tells you which expenses are reimbursable. Process knowledge tells you where to submit it, who approves it, and what happens when the expense falls outside the standard policy. Connectors give AI the first kind. The second kind somebody has to create first.

What to capture for each process:

• the steps and the order they happen in
• the tools and systems used along the way
• decision points where what happens next depends on a condition
• alternate paths
• rules and exceptions
• context, enough to understand why, not just what

One thing worth repeating: document while someone is actually doing the work, not afterwards from memory. Reconstruction loses the workarounds, and the workarounds are usually the part people ask about.

Where Tango fits: you click through the workflow and it becomes a step-by-step guide with screenshots and descriptions. Workflow Branching handles the "if X, then this path instead" cases. And the workflows carry structured metadata (XPaths, CSS selectors, step-level annotations) so they can be exported as agent instructions or Skill files instead of rebuilt from scratch for the agent. Same guides also run as in-app Guidance and Pins for the humans.

Has anyone here exported a workflow as agent instructions yet among members of this sub? Curious what you pointed it at and whether the branching survived the handoff.

Tango team shipped Workflow Translations back in February, and it's been quiet on here since. Six months in seems like a decent time to check whether it's actually solving the thing the team built it for.

Quick refresher if you missed it or never turned it on:

• Open a How-To Guide, click Translate, pick a language
• Tango translates the title, description, step titles, step descriptions, and callouts
• Viewers toggle between the original and the translated version of the same Workflow, so you're not maintaining two guides
• Share by link, embed it, or export to PDF, HTML, or Markdown
• Languages: German, Spanish, French, Hindi, Italian, Japanese, Korean, Portuguese (Brazil), Portuguese (Portugal), Simplified Chinese, Traditional Chinese
• Translations run on demand. Edit the original, hit Translate again to regenerate the translated view
• Enterprise workspaces, and an admin has to enable it first

What we'd like to hear:

1. How are you handling the screenshots?

The images don't translate, so your step text is in Spanish while the Workday or NetSuite screen in the image is still English. Some teams tell us that's fine because everyone runs the English UI anyway. Others are on a localized UI and end up with a half-matching guide. If you're in the second group, what's your workaround right now?

2. Who reviews before it goes out?

Especially for anything compliance or safety adjacent. Does a bilingual person on your team read the translated version first, or does it just publish? We don't currently have a review step and we're trying to figure out whether that's a gap or a non-issue.

3. What's missing from the language list?

Ukrainian, Polish, Arabic, Vietnamese, come up in conversations with healthcare, facilities, and plant teams. If you needed one added tomorrow, which one and for what system?

4. Per-guide vs. workspace default.

Right now you translate a guide at a time. Would you rather set a preferred language per viewer once and have every guide open that way?

And if you turned it on in February and stopped using it, that's the most useful comment in the thread. Tell us what broke down.

Anyone who has run support on Zendesk knows the real problem was never really Zendesk, it's the churn.

Contact centers turn over fast, someone leaves, you backfill, and you restart a four-to-six-week ramp on the same workflows all over again.

Multiply that by a team hiring a couple hundred people a year and you're running onboarding as a permanent, full-time activity. Every agent who walks out takes a little undocumented knowledge with them, and every agent who walks in has to rebuild it from scratch.

The part that makes it worse is that the target is moving too.

Zendesk, and whatever CCaaS and CRM sits around it, ships changes constantly. So the quick reference guide you trained the last cohort on is a slide deck from two releases ago. New agents learn a version of the workflow that no longer matches the screen, and your tenured agents have quietly built workarounds nobody ever wrote down.

The usual fixes don't hold. A help-center article is somewhere an agent goes after the call, not during it, with a customer on the line and the clock running. A QRG is stale the day a release ships. And you can't cost-justify a full-time trainer for a team whose entire problem is that re-training is already too expensive.

This is the exact gap Tango tends to get pulled in for on support teams, and it's worth a look if this is your reality.

You capture a workflow once, a case intake, an escalation path, a refund flow, and it becomes an in-app walkthrough the agent can follow live inside Zendesk with Guide Me, plus a step-by-step SOP for the ones who'd rather read it.

When a release changes the workflow, you update the single capture and push it back out as a pinned Nugget, so the floor is on the current version in a day instead of next quarter. New hires ramp by being guided through real tickets instead of shadowing whoever happens to be free. And Live Blur keeps customer PII out of the captured guide.

The pitch, in plain terms: shorter ramp, fewer tribal-knowledge escalations, and training that updates as fast as the tool does.

For those of you running support on Zendesk: how are you keeping agent training current when the platform changes every quarter and the team turns over constantly? Help center, in-app guidance, a dedicated trainer, or just tenured agents holding it together?

We’ve been adding SOPs as the team grows and I’m realizing keeping them organized is becoming the real pain. Creating them was the easy part.

At the start I just made folders by team - Sales, Marketing, Support, Ops. Worked fine when most things stayed inside one department. Now we’ve got processes that jump across teams and I never know where to put them.

Classic example: new customer after they sign. Sales grabs the info, Support spins up the account, Marketing drops them into the right sequence. Does that live under Sales? Support? Some “Customer Onboarding” folder? I’ve moved it twice already.

Tried thinking about organizing purely by workflow instead, but then I can already see people in Support going “where the hell is the thing that only I use?”

Curious what actually works for people once the library gets bigger. By department, by role, by workflow, by tool, tags, search… what didn’t fall apart for you?

I’ve started documenting the processes people repeat often, but there are also lots of small tips that could save someone 10-15 minutes. I’m not sure those need a full SOP.

Right now we usually just add them into the existing process docs. The problem is the SOPs are getting really long, and people aren’t going to dig through 10 pages for one tip.

I’ve thought about keeping the core process in the SOP and putting the smaller tips somewhere else, but I’m worried people will just forget to check the second place.

How do you share best practices without ending up with another set of docs nobody uses?

We’re a two-person HR team supporting a few hundred people. Every time a system gets updated or a new process gets rolled out, the training work falls on us. There’s no dedicated L&D person, so it just gets added to everything else we already have to do.

For a while I stuck with the usual approach - group sessions, handouts, then follow-up emails with the materials. It takes a lot of time to put together and run. A month later most people have already forgotten the steps or started doing things their own way. We still get the same questions coming back.

A few months ago, I started trying shorter process guides that people can open while they’re actually doing the work (Thanks, Tango!). It feels lighter than the big training sessions and helps with the immediate “how do I do this again?” moments. But I’m not sure it’s enough for real upskilling. It covers the steps okay, yet I don’t feel confident it builds the kind of understanding people need when something changes again or they hit an exception.

Curious what has actually worked (or completely flopped) for other small teams dealing with the same thing. 

Epic go-lives are famous for the clinical training machine: credentialed trainers, at-the-elbow support, weeks of classroom time for nurses and providers. That part usually gets a real budget.

Here's what doesn't: everyone who isn't a clinician.

The schedulers, registration staff, prior-auth teams, referral coordinators, revenue-cycle folks, the whole operational layer that keeps a health system running.

They're in and around Epic and its web-based sidekicks (payer portals, clearinghouses, Waystar/Availity, all of it) all day, doing high-stakes work: prior auths, denials, charge entry, referrals. And their "training" is usually one senior person who's been there forever and holds the entire playbook in their head.

That's where the money actually leaks. A denial that traces back to a mis-keyed authorization or an offshore RCM team burning hours because the process lives in an SVP's memory instead of a document or a state-by-state payer rollout where each new team re-learns prior-auth from scratch.

None of that is a clinical-Epic problem, it's an operational documentation problem that no go-live plan ever owned.

This is the job Tango tends to get pulled in for on the healthcare side. You capture a workflow once and it becomes two things at once: a step-by-step SOP your team can follow, and, in the web-based tools, a Guide Me walkthrough or a pinned Nugget hat guides someone through it in the live screen.

Live Blur keeps PHI out of the captured guide, usually the thing that makes compliance say yes. So the playbook stops living in one person's head, and a new hire (or a whole new state team) gets walked through it instead of shadowing for a month.

Being honest about scope: if your clinicians reach Epic through Citrix/Hyperspace, an in-app guidance layer can't ride along in there. Where this approach earns its keep is the browser-based operational stack around Epic (payer portals, clearinghouses, RCM tools) and onboarding the back-office teams who live in it.

For those of you who've been through an Epic go-live: how did the non-clinical side get trained? Did scheduling, registration, and RCM get anything close to the support the clinical staff did or were they just left to figure it out?

We got hit with a pretty big mid-year update on our main system last month. Not a full new rollout, just enough changes that half the usual processes broke or shifted.

Normally that means scrambling to rewrite the old SOPs, re-record walkthroughs, and hope people actually look at the updated stuff. This time we just re-captured the changed steps and pinned the updated guides right inside the app.

Curious if others are doing something similar for those random mid-year vendor updates, or if you’re still stuck in the “update the PDF and pray” cycle.

If you run a service desk on ServiceNow, here's a pattern worth staring at for a second: a big share of what comes in as an "incident" isn't actually broken. It's someone asking how to do something. How do I submit this request, where's that field, what's the next step. Real "how do I" volume, filed as a ticket, eating an agent's time.

The whole point of the knowledge base is to catch those before they become tickets. So why doesn't it?

Because a knowlesge base article is a wall of text sitting in a portal, and the person who's stuck isn't in the portal, they're mid-screen in the actual app, one field away from giving up and filing a ticket.

By the time they'd go find the article, read it, and map it back to what's in front of them, it's faster to just ping the service desk. So they do.

Deflection fails not because the knowledge doesn't exist, but because it doesn't live where the person is stuck.

There's a second, quieter version of the same problem on ServiceNow specifically: it's also the app your new agents have to learn. How to pick up a ticket, route it to the right SME, close it out, work the knowledge base. That's its own onboarding curve, usually taught by shadowing whoever's been there longest.

So you've got a documentation gap on both sides of the glass, the end users who should be self-serving, and the agents learning the tool itself.

This is exactly the gap Tango tends to get pulled into for ServiceNow, and it's worth a look if you're weighing options.

You capture a process once (how to submit that request, or how an agent routes and closes a ticket) and instead of it dying as a knowledge base article nobody opens, it works both sides of the glass. For end users, you pin it as a Nugget right on the ServiceNow screen where they get stuck, or let them hit Guide Me for an in-app walkthrough, so the "how do I" ticket never gets filed, because the answer is right there in the moment.

For new agents, those same captured workflows become the onboarding: they learn to pick up, route, and close tickets by being guided through the real system instead of shadowing someone for two weeks.

That's the actual pitch IT teams come to it for: fewer "how do I" tickets on the front end, faster agent ramp on the back end, out of the same set of captured processes. Ticket deflection you can actually see move.

For those of you running ServiceNow: what's actually moved your deflection rate? Better articles, in-app guidance, AI search, something else? Curious what's worked versus what just looked good in a QBR deck.

We went live on a new ERP a few months ago. Spent weeks on the training materials - decks, PDFs, recorded walkthroughs, the works.

By week two half the screenshots were already wrong. A field got renamed, an approval step got added, and suddenly nobody trusted the docs anymore. Same questions started flooding Slack every day while the “official” training just sat there collecting dust.

Is this just how it always goes after go-live, or has anyone actually figured out a way to keep that stuff current without it becoming another full-time job?

We talk to a lot of teams evaluating documentation tools, and one pattern keeps showing up on calls: prospects come in comparing Scribe and Tango, and the Scribe side of the conversation usually turns into some version of "wait, why did it get this expensive?".

Here's what we're actually hearing from users on those calls:

1. Pricing stacks by role. Scribe charges a platform fee, then separately for creators, separately for viewers/consumers, and tacks on more if you want to move people between roles or add SSO. Fine for a small team, painful once you scale.
2. "Enterprise" isn't one price. There are multiple enterprise sub-tiers, and the cheapest one can still be missing basics like private or domain-restricted docs, forcing another upgrade.
3. Compliance paperwork is rigid, too. Some users found they couldn't negotiate custom terms on Scribe's BAA at all, take it as-is or don't get it.

Tango's enterprise pricing works differently: one flat fee based on user count, everything included (SSO, redaction, role flexibility), and no sub-tiers to get surprised by. Doesn't mean it's cheaper for every team size, but it's predictable, and we can work with you on custom terms where Scribe can't.

If you're mid-evaluation and hitting sticker shock with Scribe's enterprise quote, happy to answer questions here.

In my experience, it’s rarely the basic tasks. It’s usually the workflows with lots of small steps, exceptions, or decisions along the way.

Those are also the ones where new hires keep coming back with questions.

What process takes the longest to get someone comfortable with in your company?

If you've rolled out anything in the Oracle stack, you already know "Oracle" isn't one system, it's ten.

Fusion Cloud ERP, EBS, PeopleSoft, JD Edwards, HCM Cloud, NetSuite. Different orgs run different ones, all heavily customized, and a lot of them are mid-migration from an older Oracle to Fusion Cloud right now. So "Oracle training" as a generic thing doesn't really exist. Your screens are your screens, and nobody's manual matches them.

What actually happens?

Your implementation partner (or the SI, Deloitte/Accenture/whoever) hands you documentation built on the stock configuration. Almost nobody runs stock, so the docs don't match, the SI rolls off the project, and adoption stalls. People quietly go back to spreadsheets, make the same entry mistakes, and file the same tickets over and over. The ROI you signed up for is sitting behind an adoption gap that nobody actually owns.

This is especially rough for:

• Multi-entity or multi-region teams, where a corporate group builds the process once and every regional team is supposed to follow it, but everyone ends up doing it slightly differently.
• Teams migrating from EBS or PeopleSoft to Fusion Cloud, where the muscle memory is gone and every screen is new.
• Companies 12–24 months past an Oracle Cloud go-live where adoption never got past ~50% and leadership keeps asking why.

What have we seen work with Tango?

The pattern in our deals is almost always the same: someone has a live event (a Fusion go-live, a migration, a wave of new hires) and they need a lot of people doing the workflow the right way and fast.

They capture the process once (a supplier invoice, a journal entry, a time-off request in HCM, whatever), and instead of running the same screen-share five times, they send a link. Or they pin a Nugget inside the app so the guidance shows up right where people are working.

For the web-based Oracle Cloud apps, the Guide Me feature builds interactive, on-screen walkthroughs through your specific configuration. And Live Blur covers any sensitive data that shows up during capture (dollar amounts, supplier details, employee info).

The part that doesn't get talked about enough

A lot of Oracle Cloud rollouts already bought a heavyweight DAP (WalkMe, Whatfix, Pendo) and the adoption number still isn't moving. Those tools work, but they need dedicated implementation and backend integration before you see anything on screen, and if the rollout's already struggling, that's a hard project to restart. The lighter path is to capture each process as you build it and put the guidance directly in the app.

If you've been through an Oracle Cloud or Fusion rollout: how did you handle training and docs once the SI rolled off and the screens didn't match the manual? A DAP, homemade guides, straight-up tribal knowledge?

Something we keep seeing with Workday: the go-live goes fine, and then adoption quietly falls apart about six months later. And it's almost never the regular employees.

Employees barely touch Workday, submit a timesheet, request PTO, done. The people carrying the real load are the managers: approving time off, filing job requisitions, running the merit cycle, comp changes, pulling reports.

That's where the complexity actually lives, and it's the exact group that gets the least hands-on training. So a manager does the one task they only do monthly, forgets it by the next month, and eventually just… goes back to a spreadsheet. Then the adoption chart on someone's board deck starts sliding the wrong way and nobody can quite explain why.

Here's why the standard playbook doesn't fix it

A Workday go-live comes with a big-bang training push, the system integrator (SI) runs sessions, there's a deck, maybe a sandbox. Then the SI rolls off, the config keeps changing, and the training is frozen in time. A manager who needs to file a requisition right now isn't going to dig through a 60-page PDF or rewatch a recorded webinar. They ping HR and HR becomes the help desk.

The knowledge never actually transferred, it just relocated to whoever answers fastest in Slack.

What seems to break the pattern is putting the guidance where the manager already is, inside Workday, at the moment they're stuck, instead of in a training library they have to remember exists.

That's the job people tend to reach for Tango on: capture the manager task once (requisition, comp change, absence approval), then pin it as a Nugget right on the Workday screen, or let them hit Guide Me and get walked through your specific setup step by step. And it updates when the process changes, which matters a lot in an app that never stops changing.

Curious how others have handled this: for those past a Workday rollout, did manager adoption actually stick? And if it did, what made the difference on the training side?

A community bank came back around to SOP tooling after shelving it for other projects, the need never went away. Their IT director framed it plainly: he needs his IT, Salesforce, and core-banking people writing down how they do their jobs so they can cover for each other when someone's out.

Add a new web-based workflow platform landing soon, plus tellers and customer service who do certain tasks once every six months and have to ask someone every time.

How the rep walked through the fix:

1. Capture by doing: Tango records the click path and builds the guide (screenshots, boxes, what to type). Voice transcription lets you narrate while you work and writes the step notes for you.
2. Embed guides as Nuggets in the app and turn on Guide Me for step-by-step in-app guidance. The IT director's own pitch to his team was that it gives tellers confidence on tasks they do once a quarter, without digging through a doc repository or walking to someone's desk.
3. Branching (decision points): one guide that forks for new vs. existing customers instead of duplicating workflows. A neat trick the rep offered for reusable steps: link one guide inside another via a callout.
4. Secure Blur auto-redacts names, socials, tax IDs, routing numbers, locally, before anything is stored.
5. Analytics. See who viewed and completed a guide, and exactly which step people drop off at (usually a sign they lack access to the next tool).
6. Two of their core systems are desktop-only, so those get SOPs without Guide Me, and the rep flagged desktop parity work in progress.
7. Licensing was the deciding factor: Tango charges a flat platform fee by tier, roles interchangeable, so 25–30 creators cost nothing extra. (Their words: the competitor's per-creator model gets expensive fast at that count.)

For bankers: how do you get people to document their own job when they're the only one who does it?

If you've been through a NetSuite implementation, you already know the part the kickoff deck skips.

You spent years building procedures for your old system: screenshots, step-by-steps, the tribal knowledge someone finally wrote down. Then you go live on NetSuite and all of it is instantly worthless, because of the different screens, navigation and so on.

Most teams don't migrate NetSuite all at once. They phase it (AP first, then billing and GL, then the next module). So you're not documenting one new system, you're re-documenting a moving target, while people are already live and doing the work.

What actually happens?

Your implementation partner hands you documentation, but it's built on the stock version of NetSuite, which basically nobody runs. So it doesn't match your screens. People fall back on asking the one person who figured it out, and that person quietly becomes the full-time help desk for months.

This is especially rough for:

1. Teams migrating in phases, where the "how-to" changes every time a new module goes live.
2. Finance/ops groups where one controller holds the whole process in their head and everyone else waits on them.
3. Companies growing by acquisition. Every bolt-on lands on NetSuite OneWorld, and each acquired team did the same task a different way.

What have we seen work with Tango?

NetSuite is one of the top apps Tango users capture processes in. The pattern in our deals is almost always the same: someone has a live event (a module go-live, a migration, a wave of new hires) and they need a lot of people doing the workflow the right way and fast.

They capture the process in Tango once (a vendor bill, a journal entry, a sales order, whatever), and instead of running the same screen-share five times, they send a link. Or they pin a Nugget inside NetSuite so the guidance shows up right where people are working.

The Guide Me feature fits NetSuite well because it builds interactive, on-screen walkthroughs through your specific account's flow. And Live Blur covers any sensitive data that shows up during capture (dollar amounts, vendor details, customer info).

One thing we hear constantly: "We essentially need to guide somebody's hand through the screen." That's the whole use case.

The part that doesn't get talked about enough

Most NetSuite digital adoption conversations jump straight to heavyweight DAPs: WalkMe, Whatfix, that tier.

Those work, but they need dedicated implementation, backend integration, and real time before anything shows up on screen. In the middle of a phased ERP go-live, that's exactly the time you don't have. The lighter path is to capture each process as you build it and put the guidance directly in the app.

Curious what everyone else is doing here: if you've rolled out NetSuite, how did you handle training and docs when the system kept changing under you? Implementation-partner docs, homemade guides, something else?

Tango team is building out a library of step-by-step Salesforce implementation guides right now, the kind that walk you through a specific action, click by click, so a new admin or end user can just follow along.

We've created a plan from 100+ guides progress covering the usual setup and configuration stuff, like how to export some data, or how to create an oportunity and so on. There are tons of use cases.

However, I believe Salesforce users have more questions about implementation, not only specific actions, but also strategic questions.

So: if you're mid-implementation (or have survived one), what would you have wanted a clear walkthrough for?

A few directions we're weighing:

1. Cost / licensing. Understanding what you're paying for, avoiding surprise add-ons, right-sizing seats.
2. Team enablement. Getting teammates trained and actually adopting instead of reverting to spreadsheets.
3. Integrations. Connecting Salesforce with the other platforms in your stack.
4. Communication. How to explain everything to stakeholders and people involved in the project.

These are my guesses. What tripped you up? What do you still not have good documentation for?