
The most visible change is not automation of configuration. It is the disappearance of the long, quiet hours consultants used to spend turning decisions into documents.
What genuinely got faster
| Task | Before | Now |
|---|---|---|
| Functional spec | Half a day of writing | An hour of editing a draft |
| Test scripts | Manual, repetitive | Generated from the process steps |
| Training material | Screenshot marathon | Structured draft, then polish |
| Status reporting | Copy-paste from trackers | Summarised automatically |
What got harder
Expectations. When a client believes documentation is instant, the pressure moves onto the part AI cannot do: deciding what the process should be, and defending that decision in a room full of stakeholders with different incentives.
The scarce skill is no longer producing the document. It is knowing which answer is right for this business.
Skills worth building now
- Process design and trade-off reasoning.
- Data quality assessment — AI output is only as good as the master data.
- Clear written communication, because you will be editing more than writing.
- Enough technical literacy to judge an integration proposal.
About the Author
Kirandeep Kaur
I explore technology, simplify complex ideas, and share what I learn along the way — mostly SAP, AI and enterprise tech, sometimes everything else.
More about Kirandeep →

