All articles

Aiver Ilaya
Aiver IlayaDirector, Aliso Digital
ShareLinkedIn
Aiver Ilaya, director of Aliso Digital

Written by

Aiver Ilaya.

Director of Aliso Digital, a Melbourne-based IT consultancy specialising in digital transformation programs, process mapping and documentation.

Working on a Salesforce digital transformation project for a government department was a unique and rewarding experience.

For two years, I collaborated with an Agile project team to implement Salesforce effectively while ensuring end-users could adopt the system seamlessly. The role required balancing technical expertise, stakeholder management, and a focus on user needs. Here’s an outline of my experience and what I’ve learned along the way.


Developing Training Materials That Work

One of my primary responsibilities was creating and maintaining a variety of training materials tailored to different audiences. This included quick reference guides, user manuals, and engaging ‘how-to’ videos.

Each piece of content had to align with stakeholder needs and the organisation’s broader change objectives. I quickly realised that effective training materials are not one-size-fits-all.

Some users preferred detailed step-by-step guides, while others responded better to short, visual tutorials. By gathering feedback early, I was able to refine materials to ensure they addressed real-world use cases and challenges.

I also prioritised accessibility and organisation, ensuring all training assets were easy to locate and use.


Collaborating Within an Agile Project Team

Being part of an Agile project team meant actively participating in Scrum practices, ceremonies, and daily stand-ups. I collaborated closely with developers, business analysts, and change managers to ensure the training materials stayed aligned with system updates and stakeholder goals.

One key takeaway from this experience was the importance of being flexible. Agile environments move fast, and priorities can shift quickly. I learned how to adapt, reprioritise, and deliver on tight deadlines without compromising on quality.

Close collaboration with the Change Lead was especially critical. By aligning training strategies with organisational change objectives, we ensured that the training materials supported both technical system adoption and broader cultural shifts.


Measuring Success and Improving

Evaluation was a key part of the process. After each training session, I measured its effectiveness through user feedback and performance metrics.

This helped identify areas where users needed more support or where the materials could be improved.

By integrating this feedback into the training program, we were able to continuously improve the overall adoption process.


Coaching Leadership for Long-Term Success

In addition to end-user training, I worked with team leaders and managers to strengthen their leadership capabilities.

This involved delivering coaching sessions on new ways of working and helping them understand their roles in supporting the Salesforce rollout.

By focusing on leadership coaching, we ensured managers were equipped to guide their teams through the transition effectively.


Key Lessons Learned

1. Collaboration is Everything
Working closely with SMEs, developers, and change managers taught me that open communication and teamwork are essential for successful system adoption.

2. Training Must Be User-Focused
Effective training materials address real-world challenges, not just theoretical concepts. Understanding end-user needs is critical to creating materials that drive system adoption.

3. Flexibility is Key in Agile Environments
Priorities can shift quickly in Agile projects. Adapting to change without losing focus on project goals is an essential skill.

4. Evaluation Drives Improvement
Measuring the effectiveness of training programs and integrating feedback ensures continuous improvement, which ultimately supports smoother system adoption.


Final Thoughts

The Salesforce rollout was a challenging but fulfilling project that gave me the opportunity to apply my instructional design skills in a high-pressure, fast-moving environment.

By developing tailored training materials, facilitating effective user sessions, and collaborating with cross-functional teams, we ensured the system was adopted smoothly and effectively.

This experience underscored the importance of clear communication, user-centred design, and adaptability in delivering successful outcomes.

Instructional design is not just about creating guides or videos. It’s about empowering people with the knowledge they need to navigate change confidently and perform at their best.

Read More

Related Posts

BPMN 2.0 Is the Easy Part of Process Mapping

You can learn BPMN 2.0 properly in about a fortnight. Tasks, sequence flows, exclusive gateways, parallel gateways, start events, message events, pools, lanes. Maybe 12 elements cover most real world maps. The notation is well documented, widely understood, consistent from one organisation to the next. Which means it isn’t what

The First 14 Days After Go Live Decide Whether Your Rollout Sticks

Go live day usually feels like the finish line.The launch email goes out.The project team takes a breath.Then the tickets start. The first 2 weeks after go live are where a rollout either settles in or starts to slip.That period has a name.It’s called hypercare.Most teams plan for go live,

The Quiet Negotiation Behind Every Document Review

Nobody tells you this at the start of a technical writing career. Most of the job isn’t writing. It’s getting 20 minutes from someone who doesn’t have 20 minutes. You’ve drafted the procedure, you’ve mapped the process, you’ve done the hard part. Then it sits with a subject matter expert

I Lost Contracts Over an Office Mandate. Employers Lose More

I’ve lost contracts because of an office mandate.I’ve lost gigs.I’ve lost interviews. The pattern is always the same.The interview goes well.Then comes “we need you in 2 or 3 days a week”.I say I can do 1.That’s the end of it. It was never about skill.It was about a rule.Here’s