As a technical writer or business process analyst, your work depends on other people’s knowledge.
Subject matter experts hold the detail behind the diagrams, SOPs and work instructions.
They know what really happens beyond the documented process.
They know where things break.
They know which steps exist only because of history.
But getting that knowledge out of them is not automatic.
It depends on rapport.
Without trust, information stays surface level.
With trust, the real insights come out.
🧠 Why SMEs Do Not Always Share Everything
SMEs are usually measured on delivery, not documentation.
When you ask for their time to map a process or write an SOP, it can feel like extra work.
Some worry their explanation will be misunderstood.
Others worry gaps will reflect badly on them.
If the conversation feels transactional, they will give you only the obvious steps.
If it feels collaborative, they will share context, risks and exceptions.
Rapport changes the quality of the process map.
👂 Listening Before You Start Mapping
In process mapping sessions, it is tempting to jump straight into BPMN or workflow diagrams.
Resist that urge.
Start with conversation.
Ask them to walk you through their day.
Ask what usually goes wrong.
Ask where handoffs get messy.
Listen without interrupting.
Do not rush to tidy their explanation into structure too quickly.
When SMEs feel heard, they relax.
When they relax, they speak honestly.
That honesty is where the useful detail lives.
💬 Speak Their Language Not Yours
As a technical writer or analyst, you are trained in frameworks.
SMEs are not.
Mirror their terminology.
Use their examples.
Reflect their words back before converting them into formal documentation.
This builds confidence.
It shows you respect their expertise.
Once they trust you, they will correct you and add depth.
That improves accuracy.
🧭 Make It Safe to Share the Real Process
The documented process and the real process are rarely identical.
There are shortcuts.
There are workarounds.
There are steps added after past mistakes.
If SMEs sense judgement, they will hide those details.
Make it clear your goal is to map reality, not assign blame.
When psychological safety is present, process documentation becomes honest.
Honest documentation is useful documentation.
📄 Close the Loop Professionally
After a session, send a draft of the process map or SOP.
Show them how their input shaped the output.
Invite feedback.
Thank them for their time.
This reinforces that collaboration matters.
It also builds long term relationships.
Rapport is built across multiple interactions, not one workshop.
🎯 Final Thought
Technical writing and business process analysis are people driven disciplines.
Tools and templates help, but they do not replace trust.
Better relationships lead to better process maps.
Better process maps reduce risk and confusion.
If you want depth, build rapport first.
If you want accuracy, earn it through connection.
The information is there.
Your approach determines how much of it you receive.
