What do the SOPs look like?

Practical documentation. Step-by-step where the process is sequential and the steps matter. Decision frameworks where the work requires judgement and there is no single right answer. Written for the person doing the work, not for an audit or a compliance requirement.

How do you approach training?

Mostly workshop-based and on-the-job. The goal is that the team leaves with the confidence to act. Slides and a test are useful for compliance. They do not build the kind of confidence that changes behaviour on the job. The approach is hands-on and tied to real work the team is doing.

Do I need a preceding project with you for this to work?

No. Enablement engagements are scoped independently. You provide the context on existing processes, tools, and where the gaps are, and the work is designed around that. Prior project history together is useful but not required.

What does the 60–90 day follow-up include?

It is a single structured review session. A call or in-person meeting, scheduled 60 to 90 days after the engagement closes. It is included in the project fee. The session covers what has held, what needs reinforcement, and whether any documentation needs updating based on how the team has applied the work.

Advisory

Capable team. Inconsistent output. The gap is structure.

Most teams that under-deliver have the skills already. The knowledge is siloed, the standards unwritten, and the tools underused. I fix the structure.

Start a Conversation

The situations I see most often

These are structural problems, not performance problems.

Critical knowledge sits in two or three people
When one leaves, so does the process. Everyone knows the risk. The docs backlog is eighteen months old.
New tools deployed with a two-hour handover
The platform is live. Adoption is stuck at 30%. The team uses the old method because that is what they are confident in.
The team escalates decisions that should stay with them
They can do the work. They wait for approval because there is no clear framework for when a decision is theirs to make.

What you walk away with

Structure the team can use independently, without referring back.

Processes that survive when someone leaves
Step-by-step where needed. Decision frameworks where judgement applies. Plain language throughout.
A team that makes decisions within its remit
Clear criteria mean the team knows what a good decision looks like. Escalation becomes a choice.
Tools and systems that are actually used
Confidence builds adoption. The team knows the tools and helped shape the standards around them.

How it works

Observation first. Standards built with the team, not delivered to them. A structured rollout that ends in operational independence.

Observation and gap assessment
Map how work actually gets done. Find where knowledge is concentrated, standards are absent, and decisions escalate unnecessarily.
Co-creation of standards and documentation
Built with the team, not for them. Step-by-step where the work is sequential, decision frameworks where it requires judgement.
Training, rollout, and follow-up
Structured handover with time for the team to apply the work before the engagement closes. Follow-up review at sixty to ninety days.

What clients say about the work

From clients across strategy, execution, and advisory engagements. Different sectors, different problems.

“Working with him was straightforward and collaborative. He is very detailed, reliable, and quick to translate discussions into clear, actionable steps. He also takes the time to guide and teach the team, which really helped build our internal capability. I can see why people describe him as a “walking Google” — he brings a wide range of knowledge and connects things quickly.”

Melissa Jailani

Digital Experience & Marketing Lead

“…every decision for the web site is always based on our side and Yassir best experience on the do’s and donts. The price you pay is what you get. Before production, during production and after production it is worth every ringgit spend. Hands down, the best experience and he knows what he is doing. My advice, don’t just get a web site, but get the web site. Great job Yassir, appreciate your work. The best.”

Elisa

Real Estate Negotiator

Why me

Practical over theoretical. Co-created rather than handed over.

Enablement is built into every project engagement I run. Handover, documentation, and team capability are not optional extras that get cut when time is short. They are how every project ends. This service exists for teams that need it without a preceding project.

The approach is practical rather than theoretical. I recently worked with a marketing team of eight who had six tools, no shared process for using any of them, and a single person who held all the knowledge management logic in their head. We mapped their actual workflows, wrote runbooks in language the team chose, and ran capability building through live projects over four weeks. The goal is a team that reaches operational independence through real work, with documentation they wrote alongside me and standards they had a hand in shaping.

Common questions

Answers to the questions I get asked most often.

What do the SOPs look like?
Practical documentation. Step-by-step where the process is sequential and the steps matter. Decision frameworks where the work requires judgement and there is no single right answer. Written for the person doing the work, not for an audit or a compliance requirement.
How do you approach training?
Mostly workshop-based and on-the-job. The goal is that the team leaves with the confidence to act. Slides and a test are useful for compliance. They do not build the kind of confidence that changes behaviour on the job. The approach is hands-on and tied to real work the team is doing.
Do I need a preceding project with you for this to work?
No. Enablement engagements are scoped independently. You provide the context on existing processes, tools, and where the gaps are, and the work is designed around that. Prior project history together is useful but not required.
What does the 60–90 day follow-up include?
It is a single structured review session. A call or in-person meeting, scheduled 60 to 90 days after the engagement closes. It is included in the project fee. The session covers what has held, what needs reinforcement, and whether any documentation needs updating based on how the team has applied the work.