Your Fastest Technician is Hiding Your Documentation Problem

A tech who has lived in IT Glue for five years can pull the domain admin password for his biggest client in two clicks. Ask that same tech for the firewall config of a client he last touched in January and the guessing starts. He runs a search, gets a wall of near-identical titles, backs out, opens the org, scans the sidebar, clicks into a folder, scrolls. The first lookup took four seconds. The second took six minutes with a user holding on the phone.

Both lookups ran through the same platform. Only one of them was ever really supported by it.

The Two-Click Trick

Most operators will tell you their documentation platform is easy to get around. Press a little and you find out what they mean: the routes they personally burned in are easy. Client logos pinned across the top of the dashboard. A favorites list trimmed down to the fully managed accounts. Popular and recently used passwords sitting right on the org page, which covers roughly 80 percent of password lookups in two clicks. And nine times out of ten, a tech opens the documentation platform to grab a password, so those two clicks carry the entire day.

None of that speed came in the box. Operators assembled it themselves: favorites lists, client logos they uploaded by hand, dedicated browser windows that exist solely to keep documentation one keystroke away, homemade links pages doing the job of a dashboard. The platform supplied folders and a search bar. The speed came from years of repetition by one specific person.

Worth naming the cause here: the muscle memory exists because search failed first. Nobody bothers memorizing a route to something a search reliably finds. Two-click rituals are what a team builds after a decade of search results they stopped trusting.

In my opinion, this is the most under-diagnosed problem in MSP documentation. The tool gets credit for navigation that actually lives in the technician's head.

Off the Memorized Path

A memorized route works until the day's work steps off it. Then the platform has to carry the tech, and this is the moment clicks turn into guesses.

Search matches titles, and titles repeat by design: Standard practice is to name the global admin credential identically for every client, something close to "M365 Global Admin." That convention keeps a single org tidy. It also means a search on "365" across a few dozen clients returns a stack of indistinguishable entries, and the tech is back to browsing.

Browsing means clicking and scrolling: Operators are precise about this distinction. An extra click on its own is tolerable. An extra click plus a scroll through a long asset list, on a 13-inch laptop in the field with half the columns pushed off-screen, breaks the rhythm of whatever the tech was doing. Techs working small screens spend real effort rearranging columns and views just to keep the data they need visible, and the platform forgets those arrangements between sessions.

The org list is polluted: Teams that have lived in one platform for seven or eight years describe the org list with that exact word. Vendors, dead clients, and one-off projects crowd the same dropdown as the eighty accounts that matter. Even the first click of the famous two means scanning past entities nobody has billed in years.

Context resets midway through the trip: Change the org in one part of the interface and the list on screen doesn't always follow. The tech pauses mid-incident, unsure which screen is even live. That hesitation is small, and it lands at the worst possible moment, when someone is waiting on a fix.

A Service Desk Tech under the gun during live troubleshooting doesn't get to browse calmly. The folder tree was built during a quiet onboarding eighteen months ago. The incident is happening now.

Three Costs That Never Hit an Invoice

The two-click trick has real costs. They just never show up on the same screen as the trick itself.

New hires inherit zero routes: The Senior Tech's speed is personal property. Onboarding a new tech turns into a guided tour of two dozen private shortcuts, followed by months of the new person wearing in their own. The documentation was supposed to make knowledge transferable. The navigation layer made it personal again.

Off-route lookups bleed minutes all day: The 80 percent of lookups served by memory feel free. The other 20 percent each cost five or ten minutes of guess-and-check, and they cluster around exactly the clients and assets the team knows least, which is when documentation matters most.

Workarounds become their own inventory: Favorites docs, links pages, hand-uploaded logos, that dedicated browser window. Every one of them helps, and every one of them is another unowned artifact that decays the moment routine changes. Operators describe the result as a glorified file explorer with a personal cheat sheet taped to the front.

None of this shows up in a tooling review. The platform demos fine, the renewal goes through, and the owner keeps paying for navigation the team performs themselves. While the per-lookup cost feels small, an eight-person Service Desk runs hundreds of lookups a day. Every one of them rides on either a memorized route or a guess.

Retrieval Over Routes

I'll be honest about the bar here. Two clicks from anywhere to the password you use every day is fast. Any platform that asks techs to give that up and type a sentence instead has to win on the lookups memory can't serve, and it has to close the gap on the ones memory can. Muscle memory also has a powerful ally in frustration. When a lookup drags during week two of a migration, the tech bounces back to whatever tool their hands already know, and the switch stalls right there.

We built Lexful around describing what you need instead of remembering where it lives. The mechanics that matter for this specific pain:

Lex reads content instead of matching titles: Ask for the domain admin password at a specific client and Lex works through context, relationships, and descriptions to find it, even when forty entries share the same name. The tech never needs to know what the asset is called or which folder a predecessor filed it under.

Scope follows you: Set Lex to one org and it answers inside that client only. Open the scope to everything and a quick Command-K search or a question to Lex covers the whole book of business. No mid-trip context resets.

Naming conventions get repaired in bulk: Ask Lex which clients deviate most from your naming standards and it produces the list, then proposes the renames for approval. The convention problem that breaks title search gets fixed once, with a human approving the change, rather than worked around forever.

Tags replace the folder tree: A favorites tag takes one filter to surface and belongs to the whole team. The two-click access pattern stops being one tech's muscle memory and becomes shared structure anyone can use on day one.

That last point is the one I'd weigh hardest. A shared favorites tag survives turnover and shows up for the newest tech on their first shift. A memorized route leaves with the tech who built it.

Try This With Your Own Team

Pick the client your team touched least this quarter. Ask your newest tech to find the firewall credentials, the ISP account number, and the backup runbook, and time it. Then ask your most Senior Tech to do the same for a client they know cold, and watch how differently the platform performs for each of them. Most owners never run this comparison. The platform feels fast under hands that already know it, and the owner's hands usually know it best. The gap between those two numbers is memory doing unpaid work on the platform's behalf, and that unpaid work is the first thing to fail when you grow. A new hire exposes it. So does a departure, or an incident at the one client nobody remembers well.