ProductSomeone using a piece of software or a service daily for their own work

When I must use a new tool for my work, I want to become fluent quickly, so I do not spend weeks working more slowly than before.

Khi tôi phải dùng một công cụ mới cho công việc, tôi muốn thạo đủ nhanh, để không mất mấy tuần làm việc chậm hơn trước.

Job context

Guides teach features rather than work
High
You learn what each button does and not how to do your job.
Root cause: Documentation is written by whoever built it rather than by whoever uses it
The work continues during the learning
High
Nobody lowers the targets for that period.
Root cause: Learning time is not in the work plan
The old way is faster for weeks
High
So people go back to it.
Root cause: Any new tool is slower before fluency
Nobody to ask when stuck
Medium
Because the whole team is new too.
Root cause: The whole organisation moves at once, so nobody has experience
Nobody asked whether the tool was needed
Medium
The decision was made before you heard.
Root cause: End users are absent from the selection process

A solution is not the same thing as a product, a customer can hire a behaviour or a workaround too.

Watch the official tutorials
Product
Readily available, teaching the product rather than your job.
Learn from whoever in the team got there first
Behaviour
The most effective route, spending a colleague's time.
Work it out while doing real work
Behaviour
How most people actually learn, slow and error-prone.
Keep the old way running in parallel
Workaround
Reduces risk by extending the period of doing everything twice.
Attend the organisation's training session
Service
Present in the plan, usually held before there is real work to apply it to.

Documentation is written by whoever built the product, so it is organised by feature, while a learner needs it organised by their own work.
Why existing solutions fail: The builders know every feature and not the daily work of any particular user, so they can only write along the axis they know, and nobody funds rewriting it along the other.
Potential opportunity: Having fluent users write work-shaped guides, treated as part of the rollout.
The decision to change tools is made by management while the cost of relearning falls on the daily users, and that cost appears in none of the decision's arithmetic.
Why existing solutions fail: The business case for a system change counts licence and implementation cost and not the thousands of hours users lose to slowness, so every change looks cheaper than it is and nobody is granted time to learn.
Potential opportunity: Making user learning time a costed line inside the change decision itself.