Author: Tina

My journey with education technology did not begin with platforms, systems architecture, or artificial intelligence. It began in the classroom — with lesson plans, learners’ questions, moments of confusion, and moments of clarity. Like many educators, I entered the profession believing deeply in education as a space for growth, even if I did not yet have the language to articulate what that growth truly required.

Over time, my career evolved from teaching to curriculum and instructional design, then into quality systems, followed by learning operations, and most recently into education technology.

Looking back, these transitions were not random shifts, but layered progressions. Each role added a new way of seeing learning — pedagogy, structure, systems, and scale.

Through this journey, my understanding of education technology has changed profoundly. What once felt like supportive tools now feels like an ecosystem that shapes behaviour, access, equity, and possibility. Reflecting on education technology across yesterday, today, and tomorrow is therefore not theoretical for me — it is deeply lived.

Yesterday: Education Technology as Support and Substitution

In the early stage of my career as a lecturer, education technology was largely about supporting instruction, not redefining it. PowerPoint replaced handwritten notes. Videos supplemented explanations. Online platforms became repositories for materials and assignments. Technology was seen as an enhancement — something that made lessons clearer, more engaging, or more efficient.

Yet the classroom structure remained largely unchanged. The teacher was still the authority. The curriculum was fixed. Learners progressed at the same pace, regardless of individual differences.

I used technology enthusiastically, but uncritically. If a tool worked and helped me deliver content better, it was considered effective. The dominant question then was, “How can I teach this better with technology?” rather than, “How might learning itself change because of technology?”

Looking back, this phase reflects how education systems historically approached EdTech: as a digital substitute for existing practices. Worksheets, lectures, and assessments were digitised — but pedagogy remained intact. Learning was still measured by completion and recall rather than application or mastery.

This was not a failure of technology. It was a reflection of how narrowly we understood learning at the time.

From Teaching to Design: When Technology Exposed the Gaps

My transition into curriculum development and instructional design marked the first major shift in how I perceived education technology. Designing learning at scale forced me to confront uncomfortable truths. Content alone was not enough. Well-written materials did not guarantee engagement. Carefully planned outcomes did not always translate into consistent delivery or learner competence.

This is where education technology became more than a delivery mechanism — it became a mirror.

Learning platforms revealed drop-off points. Assessment systems highlighted misalignment between outcomes and evaluation. Analytics surfaced patterns of struggle that individual classrooms often concealed.

As an instructional designer, I began to see technology as an enabler of intentionality. It allowed us to:

• Align learning outcomes, activities, and assessments more rigorously
• Design learner journeys rather than isolated sessions
• Test and iterate learning experiences
• Capture data that informed continuous improvement

The focus shifted from teaching content to designing learning experiences. Technology supported this shift not by being innovative, but by being structured, traceable, and scalable.

Yet even at this stage, EdTech remained largely curriculum-centric. The learner experience improved, but systems were still often designed around programmes rather than people.

Today: Education Technology as an Operational and Strategic System

My move into quality assurance then learning operations fundamentally changed how I see education technology today.

At the operational level, EdTech is no longer optional. It is the infrastructure that holds modern education together. Learning management systems, assessment platforms, analytics dashboards, content repositories, and collaboration tools now form interconnected ecosystems that determine how learning is governed, delivered, monitored, and improved.

From this vantage point, technology is inseparable from:

• Scalability
• Compliance
• Quality assurance
• Standardisation
• Risk management

A well-designed curriculum can fail without the right systems to support it. A strong faculty can struggle without operational clarity. Education technology amplifies both excellence and weakness.

One of the most significant changes in today’s EdTech landscape is the prominence of data. Learning is no longer invisible. Participation, progression, performance, and engagement can be tracked and analysed. Decisions can be evidence-based rather than anecdotal.

However, this also introduces tension.

As someone responsible for learning operations, I have seen how easily data can be misunderstood or misused. Dashboards can prioritise activity over learning. Metrics can create pressure rather than insight. Technology can slip from enabler to enforcer.

Today’s challenge, therefore, is not access to technology — but governance, capability, and intent.

Stepping into EdTech Leadership

Starting my role as an EdTech Manager feels like standing at the intersection of pedagogy, technology, and strategy. This role has sharpened my belief that education technology should not lead education — it should serve it.

Platforms must align with institutional philosophy. Tools must support educators, not overwhelm them. Innovation must be purposeful, not performative.

At this stage of my career, I no longer ask whether a tool is advanced. I ask:

• Does it improve learner experience meaningfully?
• Does it support educators’ professional practice?
• Does it enable quality, equity, and sustainability?
• Does it align with long-term educational goals?

EdTech leadership today requires more than technical fluency. It demands systems thinking, change management, ethical judgment, and deep respect for the human dimension of learning.

Tomorrow: Education Technology as Intelligent, Invisible, and Human-Centred

When I think about the future of education technology, I do not imagine more platforms or features. I imagine simpler, smarter, more human-centred ecosystems.

Tomorrow’s EdTech will likely be:

• Adaptive, responding to individual learner needs in real tim
• Embedded, seamlessly integrated into learning and work
• Skills-focused, emphasising demonstrated capability over seat time
• AI-supported, but human-governed

Artificial intelligence will increasingly support curriculum design, assessment, learner support, and analytics. AI tutors, feedback engines, and learning companions will reduce administrative load and allow educators to focus on higher-value interactions.

However, the most important shift will not be technological — it will be philosophical.

Education will move from:

• Standardised pathways to personalised journeys
• Time-based progression to mastery-based learning
• Static qualifications to stackable, lifelong credentials

In this future, the role of institutions and EdTech leaders will be to ensure that technology amplifies human potential rather than replaces human purpose.

Ethics, accessibility, data privacy, and inclusivity will no longer be secondary considerations. They will be central to EdTech design and governance.

My Personal Commitment Moving Forward

Reflecting on my journey — from teaching to designing, from operations to EdTech leadership — I realise that each stage has shaped how I understand the responsibility that comes with education technology.

• Yesterday taught me the importance of clarity and engagement.
• Today taught me the power of systems and data.
• Tomorrow demands that I act as a steward of learning ecosystems.

As EdTech professionals and leaders, we are not merely implementing tools. We are shaping how people learn, adapt, and access opportunity in an increasingly complex world.

The future of education technology will not be defined by how advanced our systems are, but by how thoughtfully we design them — with learners, educators, and society in mind.

Conclusion

• Education technology yesterday supported teaching.
• Education technology today enables systems.
• Education technology tomorrow must serve humanity.

Standing now in new role, I am convinced of one thing:

“Technology will continue to evolve, but education must remain deeply human.”

Our task is not to chase innovation, but to design learning environments where technology quietly, ethically, and intelligently empowers people to grow.

And that, truly, is what I aspire to bring to the table.

I didn’t start my career intending to become someone who thinks deeply about learning systems.

I started as a lecturer — teaching students who came to class expecting knowledge, structure, and clarity. Later, I moved into a professional body, designing qualifications and certifications. Then I entered Learning & Development (L&D) in a corporate environment, where learning was supposed to translate directly into performance. Along the way, I also had a front-row seat to the realities of workplace training through my husband, a certified trainer — witnessing the pressure, expectations, and invisible work behind every “successful” training programme.

Across these roles, one thing became increasingly clear to me:

“We keep using the word learning — but we mean very different things.”

And when we confuse teaching, training, and training for professional certification, people don’t just feel bored. They feel exhausted, disengaged, and quietly resentful of learning that doesn’t help them do their jobs better.

Teaching: Building Understanding That Transfers

Teaching is where my journey began. In teaching, the goal is understanding. Knowledge must stand independently of context. Students are expected to grasp concepts deeply enough to explain them, critique them, and apply them across scenarios that may not yet exist. A good teaching question sounds like:

“Do you understand this concept in principle?”

Time is generous. Exploration is encouraged. Assessment measures comprehension, reasoning, and intellectual clarity. Teaching is not rushed, because understanding cannot be rushed. And importantly:

“Teaching does not promise immediate performance. It promises cognitive readiness.”

A student who understands a concept doesn’t just repeat what they’ve been taught. They can adapt it when the environment changes, when the tools change, when the problem looks different.

That, I realised early on, is the essence of teaching — building understanding that lasts.

Training for Professional Certification: Understanding Meets Competence

Years later, I joined a professional body, where I began designing qualifications. What I get to see with “professional certification” is that it is structured, controlled, and high-stakes. I had to consider:

• What must every competent professional know?
• What can reasonably be self-studied?
• What requires formal instruction?
• How do we assess competence fairly?

On paper, the learning pathways were labelled “self-study”, and in practice, flexibility existed — formal structured learning was optional but always available. Still, the syllabus was tightly controlled. The right to train was granted only to accredited trainers and approved training agencies.

Why?

“Because professional certification is not just about learning. It is about standards, trust, and accountability.  Being certified carries a promise that a professional has met a defined, agreed-upon standard of competence.”

This promise cannot rely solely on informal learning or on-the-job experience. It requires structure, formal assessment, and clear boundaries.

Some experienced professionals push back – they say:

“I’ve been doing this for years. Why do I need certification? My work speaks for itself.”

In many ways, it does. But professional certification was never designed to judge individual brilliance. Professional certifications exist because systems need shared, portable standards. From a design perspective, experience is not ignored — it is refined. The modules are curated meticulously by industry experts, debated across committees, and stress-tested against current practice and future demands.

“Professional certification takes what practitioners already know and aligns it with agreed industry standards, ethical boundaries, and future expectations. Without it, experience remains personal, but with it, competence becomes accountable.”

It does not replace experience.

It sharpens it.

Most importantly, it doesn’t end once you pass the exam.

To maintain credibility, certified professionals are obliged to undertake a defined number of learning hours through structured or unstructured learning activities. This is known as Continuous Professional Development (CPD). CPD ensures practices stay relevant, knowledge stays current, and the promise behind the professional certification continues to be meaningful. The professional certification is the baseline, and CPD is the ongoing commitment to remain credible and capable.

Training: Seeing the Real Work of a Corporate Trainer

Through my husband, I gained another perspective on learning — the world of corporate training. He started as an independent trainer, delivering workshops to diverse clients. Later, he joined an organisation as their in-house corporate trainer, responsible for designing, delivering, and measuring learning outcomes across multiple teams.

Through him, I saw the real work behind the title “trainer” – it’s not just standing in front of a room and talking. It’s pressure, preparation, and precision:

• Pressure from expectations: Learners come with different backgrounds, skills, attitudes and motivations. Some are there to learn, to improve themselves; others attend only because it’s mandatory. Trainers must meet everyone’s needs while keeping the session relevant and engaging.
• Pressure from outcomes: Organisations want results. Bosses want their people to have the skill to get the job done. Training isn’t just “sharing knowledge” — it’s to improve performance, a fixing method, skill application, and behaviour change. Trainers are accountable for these outcomes, often under tight timelines.
• Aspiration and craft: Good trainers aspire to more than delivery. They craft content carefully, anticipate challenges, design exercises that resonate, and measure transfer of learning. They balance engagement, relevance, and rigor, all in real time.

Watching him, I realised that being a corporate trainer is part pedagogue, part psychologist, part project manager. You need empathy to understand your learners, influence to manage their bosses, strategy to design meaningful programmes, and stamina to deliver consistently under scrutiny.

It also made me appreciate why some workplace learning succeeds, and some fails. A trainer’s skill can be brilliant, but if the system, expectations, or support is misaligned, even the best facilitator cannot make learning stick.

One thing he often emphasises is:

“Training is meant to improve performance, not dwell on theory. Yet, there is no such thing as ideal. We can’t run away from having to face some content that is inherently theory-heavy — complex systems, workflows, or technical tools. The challenge is structuring and delivering it, so learners remain engaged, connected to outcomes, and able to apply knowledge.”

I saw this in action when he designed a system training module for his organisation. The module had a theory-heavy prerequisite delivered via e-learning, covering concepts staff had to understand before touching the system. Instead of letting it remain a dry, abstract experience, he implemented a hybrid approach:

• Learners completed the e-learning module at their own pace, ensuring baseline knowledge. This became the pre-requisite before the classroom session.
• Classroom sessions were hands-on, scenario-driven, and performance-focused, where learners applied concepts directly to tasks they would perform at work.
• Exercises simulated real work conditions, allowing learners to practice, ask questions, and build confidence before independent application.

This approach struck a balance – learners were prepared and knowledgeable, yet the training remained practical, relevant, and performance-oriented.

Watching him, I realised that:

“A good training design is both art and science. It cannot always be a one-size fits all approach. You have to respect theory when necessary but always keep one eye on the end goal – the learners’ competence and capability in the real world.”

This brought me to a principle I now hold dear – training at work should always have a purpose. Even when you attend sessions on communication, personal grooming, or presentation skills, the goal is not just self-improvement — it’s about being better at your role, projecting credibility, and performing effectively.

Training should be intentional, focused on reskilling or upskilling, and delivered based on actual need, not “just because there’s a course available.”

When the purpose of training is clear, relevant and measurable in the work, people:

• Engage meaningfully
• Apply skills immediately
• Retain knowledge
• Take ownership of their development

Without purpose, training risks becoming checkbox learning — attendance driven by perks, not by progress.

Seeing the Differences Clearly

Across my experiences, I’ve learned to articulate the differences between teaching, performance training, and training for professional certification clearly:

Each has its place, each has its limits, and problems arise when we ignore these boundaries.

Standing in Between: What I’ve Learned

I spent my career moving through these worlds – teaching, qualification design, and performance training.

I wasn’t “just a lecturer”.

I wasn’t “just L&D”.

I wasn’t “just a qualification designer”.

I was someone who stood between theory and practice, understanding where learning is about understanding, where it is about doing, and where it is about proving competence.

That perspective allows me to see:

• When teaching is essential
• When training is enough
• When certification must hold the line

And if I reflect on all these experiences, a simple truth emerges:

• Teaching should focus on understanding and transferability
• Performance training should focus on immediate competence in context
• Professional certification training should ensure understanding plus evidence of competence

The difference between how it should be and how it actually is, is obvious — and that gap is where learning leaders must act.

Not rush training for compliance.

Not compress learning for speed.

Not overload classrooms with “just in case” theory.

Learning should not exhaust people. It should enable them.

And when each form of learning is designed — and respected — for what it truly is, learning doesn’t just happen.

It works.

In my experience working at the intersection of curriculum and learning & development frameworks, both processes felt familiar. Each follows a structured cycle of analysis, design, implementation, and evaluation — the logical sequence any learning professional would recognise. What differentiates them, however, are their intent and impact.

A curriculum framework operates at the micro level — it is educational, instructional, and learner-centred. It defines learning experiences, content, and assessments to develop specific capabilities, translating strategic intent into tangible, measurable learning journeys that progress logically over time. An L&D framework, on the other hand, operates at the macro level — it is organisational, strategic, and systemic. It identifies the capabilities the organisation needs to thrive, whether in leadership, communication, or digital literacy, and ensures that learning aligns with business priorities, culture, and performance outcomes. In short, it is the architecture of learning at scale, designed to shape the workforce for what’s next.

In a corporate ecosystem, the L&D framework sets the direction, while curriculum frameworks bring that direction to life. And at the heart of it all — the real audience is the employees themselves.

Recently, I found myself asking a question that felt both simple and profound:

• How do employees in Malaysia really feel about their organisation’s learning initiatives?
• Do they see them as a genuine pathway to growth — or just another HR process that looks good on paper?

To explore this, I decided to collect some data myself. Not as part of a formal research project, but out of genuine curiosity. I wanted to understand, from employees’ perspectives, how learning opportunities are communicated, accessed, rewarded, and supported in real workplaces today.

Want to be a part of this? [Take the survey here]

My early findings mirrored what I had long suspected: employees want to learn. They are eager to grow, stay relevant, and contribute meaningfully. But structural and cultural barriers persist — and they have a real impact on how learning happens at work.

Research supports this too. Studies by LinkedIn Workplace Learning Report (2024) echo what many of us already know:

• Workload remains the biggest obstacle to learning.
• Communication on upskilling and reskilling opportunities is often inconsistent.
• Recognition is unclear — only a fraction of organisations link learning milestones to rewards, promotions, or visibility.

The result? Employees navigate a maze of opportunities without a map. They see programmes, but not pathways. Initiatives, but not impact. And when learning feels disconnected from growth, participation becomes compliance, not commitment.

As the designer of learning systems, and a participant within them, here’s what I’ve learned about what makes learning work:

✅ 1. Communication Builds Clarity

Employees can’t align with what they don’t understand. Learning & Development strategies must be communicated with the same intensity and clarity as business goals — repeatedly, transparently, and in ways that connect to personal growth. Without clarity, even the best-designed L&D strategy risks becoming noise.

✅ 2. Structure Builds Trust

When people know how to enrol, what criteria apply, and what outcomes to expect, they engage with ownership. Ambiguity erodes trust; structure builds it. A good L&D framework provides a roadmap — making learning accessible, predictable, and equitable.

✅ 3. Recognition Sustains Motivation

Motivation doesn’t always need to be monetary. Recognition can come in many forms — certifications, project leadership opportunities, internal visibility, or acknowledgment from managers. What matters is fairness and visibility. Without it, engagement fades and learning becomes transactional.

✅ 4. Balance Sustains Performance

As the LinkedIn Workplace Learning Report (2024) highlights, nearly half of global employees (49%) say workload prevents them from pursuing learning. Organisations that provide protected learning time or adjust workloads consistently see higher engagement and retention. Real commitment means making space for growth, not just preaching it.

Another point worth mentioning on why learning initiatives often struggle is the way organisations separate talent strategy and learning strategy. Talent strategy focuses on identifying, developing, and retaining high-potential employees for current and future roles. Learning strategy focuses on designing and delivering programs that build skills and capabilities. When these functions operate in silos — sometimes even with different owners and KPIs — learning and talent can feel like competing priorities. Learning teams may focus on course completion metrics, while talent teams focus on succession or retention goals. The result? Initiatives are disconnected, employees are confused, and the organisation misses the opportunity to develop people holistically.

Bridging this gap requires integration, alignment, and shared ownership. Learning becomes a tool to grow talent, and talent strategy becomes a lens through which learning programmes are designed.

Another observation to add on is the trends in Malaysia’s learning landscape these days – Malaysia’s economic growth is being driven by digital transformation, manufacturing innovation, and a renewed services sector. This shift is redefining what L&D frameworks must deliver. Three trends have came to the spotlights:

✅ 1. AI and Automation Are Rewriting the Skills Playbook

Core skills now include AI literacy, digital adaptability, and continuous learning. L&D frameworks must evolve from static competency models to dynamic, continuously updated capability ecosystems.

✅ 2. Employees Want Learning to Be Meaningful, Not Mandated

Learning requires space, focus, and support. It’s not about the number of courses completed, but the depth of growth achieved.

✅ 3. Environment Shapes Motivation

Culture matters. When peers and leaders value growth, curiosity spreads naturally. When learning is treated as an afterthought, enthusiasm fades — no matter how good the content is.

Despite initiatives, 77% of APAC employers report difficulty filling roles, especially in data and tech (ManpowerGroup, 2025). This isn’t just a hiring issue — it’s a development issue. Organisations can’t recruit their way out of a skills gap; they must develop their way out.

The way I see it, it’s time we create the human-centred future of learning. The foundation is already there: a workforce eager to learn. What’s needed now is alignment, clear pathways, and leadership that sees learning not as an interruption, but as an investment. Learning should mirror growth — fluid, flexible, and human. It should encourage curiosity, not compliance; reflection, not repetition. Successful L&D frameworks balance structure with empathy, celebrate milestones while focusing on meaning, and connect learning not just to performance, but to purpose. When learning becomes part of the organisational DNA — woven into conversations, performance reviews, and leadership decisions — culture changes. Employees begin to see growth not as an expectation, but as a shared journey.

Looking back, my journey from curriculum design to L&D strategy reminds me: learning is never static — it evolves as people do. The curriculum framework taught me precision — to think about sequences, outcomes, and assessments. The L&D framework taught me vision — to connect learning with culture, systems, and strategy. Both are necessary. One provides the how; the other ensures the why. And more importantly, both remind me that learning, at its core, is relational. It’s about people — their stories, aspirations, and the systems that either support or stifle their growth.

My hope is simple: That one day, every employee can proudly say —

“My company’s learning culture doesn’t just demand growth from me; it grows with me.”

There’s a peculiar kind of silence that lingers in organisations that run purely on legacy knowledge. It’s not the silence of inactivity—it’s the silence of familiarity. Everyone knows what to do, but no one quite knows how they know it. Things just work—until they don’t.

When I first walked into such an environment, the company had been operating for decades without structured documentation. Processes were embedded in people, not paper. The ones who “knew how things worked” had been there for years, sometimes decades. SOPs, process maps, reference manuals are presented like habits, muscle memory, and the occasional Excel sheet that everyone swore was “the latest version.”

Gulp!

As someone whose professional grounding has always revolved around building structure, I have always believed that institutional excellence begins with clarity. But clarity doesn’t appear on its own—it needs to be designed, validated, and communicated. My mission was to turn tacit knowledge into explicit systems: to write the SOPs that never existed.

How did I do that?

Step 1 – Understanding the Unwritten

Before writing a single word, I needed to understand the unwritten rules. I learned quickly that legacy organisations don’t resist documentation because they’re careless—they resist it because it threatens the familiarity that makes their work feel stable.

So instead of starting with templates, I started with people. I spent time shadowing teams—sitting beside coordinators, analysts, and trainers; listening to how they explained things to new hires; and noting down what they did differently from what others claimed to do. These were not formal interviews but conversations of trust.

When I asked, “How do you usually do this?”, the answer often began with, “Normally we…” followed by a mix of “but sometimes…” and “it depends.”

That was my first insight — the SOPs didn’t just need to document the process; they needed to capture the logic behind the decisions.

Step 2 – Mapping the Chaos

Legacy processes are rarely linear. They grow organically—layer by layer, patch by patch. To make sense of them, I used a bottom-up process mapping approach.

Rather than starting with a departmental workflow, I identified process clusters—recurring patterns of activities that led to specific outcomes. For instance, in a learning operations environment, “course activation” could involve HR, content, logistics, trainers, and even finance. Everyone had a hand in it, but no one owned the end-to-end picture. Using visual process maps (I prefer Lucidchart or Miro), I traced each step as it was currently done, not as it should be done. That distinction was crucial.  Documenting “ideal processes” too early can alienate those who actually run them. By mapping the reality first, I earned credibility, and most importantly, people saw that I wasn’t here to “change everything,” but to understand.

Once the as-is map was complete, I would gather the stakeholders in short, focused sessions to validate it. This often led to surprising discoveries: redundant approval loops, outdated forms, or responsibilities that had shifted over time without anyone realising it.

Step 3 – Defining Ownership and Accountability

In companies that run on legacy knowledge, ownership is fluid.

“We’ve always done it this way” often translates to “we’re not sure who’s in charge.”

So, the next step was to clarify process ownership. Every SOP, no matter how simple, needed to answer one key question – Who owns this process from start to end? This was not a matter of hierarchy—it was a matter of clarity. For example, if a process involved four departments, one had to be the process owner (responsible for ensuring compliance and improvement), while others were contributors.

Introducing this concept wasn’t easy. It required diplomacy and empathy. In some cases, it meant revisiting turf boundaries. But over time, people began to see the value—when ownership was clear, so were expectations.

Step 4 – Writing for the Reader

Once the groundwork was set, it was time to write.

I believe that SOPs are not just documents—they are learning tools. They need to be simple enough for a new hire to follow yet detailed enough for an auditor to verify. So, I structured each SOP with three key sections:

• Purpose and Scope – Why the SOP exists and what it covers.
• Roles and Responsibilities – Who does what, clearly stated.
• Step-by-Step Procedure – The actual process, written in a concise, active voice, supported by visuals or decision trees when needed.

For each procedure, I included “critical control points”. These are steps that could impact compliance, customer experience, or data accuracy. These would help transform the SOP from a static manual into a dynamic quality tool.

Step 5 – Validation and Continuous Feedback

No SOP should ever be written in isolation. Once drafts were ready, I organised validation walkthroughs, for example, live sessions where process owners would perform the tasks using the draft SOP as their guide.

This was often where the magic happened. Watching someone struggle to find a step or interpret an instruction revealed exactly where the SOP failed to communicate. One of the most important lessons I learned was this:

“The effectiveness of an SOP is not in how it reads, but in how it guides”.

Through each round of feedback, bear in mind that the documents will evolve not only in accuracy but also in voice, gradually beginning to sound like the people who use them rather than like corporate templates written by outsiders.

Step 6 – Implementation and Change Management

Documentation is the easy part. Adoption is the real challenge. I quickly learned that rolling out SOPs is a change management exercise, not just a documentation project. Legacy organisations have muscle memory and changing that requires more than a PDF upload to the shared drive.

To encourage adoption, I used three key strategies:

• Microlearning orientation: Short sessions introducing each SOP and why it mattered.
• Champion system: Appointing process champions within departments to answer questions and reinforce consistency.
• Feedback loop: Creating a formal channel (e.g., monthly review form or MS Teams chat) for users to flag inconsistencies or propose improvements.

Over time, what started as a documentation initiative evolved into a culture of accountability. Teams began using SOPs as a reference, not as a chore. The technical steps are one thing, but the human side was the real learning curve.

I remember one senior staff member telling me, “I’ve been doing this for 15 years. I don’t need an SOP to tell me how.” She was right, in a way. She didn’t need it—but the organisation did.

Even my own boss, once said, “SOPs are a waste of time – everyone already know how to do it from the back of their head. The rest should learn the same way – we don’t need to spoon-feed them!“

This moment reminded me of the delicate balance between respecting expertise and institutionalising knowledge. The goal was never to replace people’s experience, but to preserve it—so that when they move on, retire, or change roles, the organisation doesn’t start from zero again.

Through empathy, consistent communication, and genuine curiosity, I began to see attitudes shift. When people felt heard, they became open to documenting their own workflows. Some even took ownership by proposing improvements or volunteering to pilot-test new templates.

The success of an SOP initiative CANNOT be measured only by the number of documents completed. Real impact shows up in how people work differently.

At the end, what does success look like here?

• New joiners were able to onboard faster.
• Cross-departmental miscommunications reduced because everyone now had a shared reference.
• Quality checks became easier because expectations were clear.
• Most importantly, decision-making became more transparent.

Imagine, ISO auditors reviewing the documentation, and commented that your SOPs “reflected how people actually worked,” not just theoretical procedures.

That, to me, is the ultimate validation.

Writing SOPs in a legacy-driven company is less about writing and more about translating culture into structure. Writing SOPs is not just a technical task—it’s an act of transformation. You are, in essence, building the bridge between legacy and sustainability.

What began as a documentation project often turns into a cultural awakening. You start by asking, “How do you do this?” and end up uncovering why things are done this way. Along the way, you learn that documentation is not about control—it’s about continuity.

For me, this experience reinforced a belief I’ve always held – operational excellence begins with clarity, and clarity begins with people.

The most meaningful SOPs I’ve written were not those that ticked every compliance box, but those that gave people a sense of structure, pride, and confidence in their work. They became, in many ways, a mirror of the organisation’s collective wisdom—finally captured, finally shared, and finally ready to evolve.