I’ve evaluated and introduced new technology across the business, from operational platforms to AI tools. My role was to understand the problem we were trying to solve, determine whether the tool fit how the team worked, and then help turn the decision into something people could realistically adopt.
Our social media workflow had become unnecessarily manual. Client approvals happened in spreadsheets, posts had to be re-entered into publishing tools, reporting was fragmented, and the process was hard to scale.
I evaluated multiple platform options against the team's actual workflow needs. We ultimately selected Hootsuite, and I built the business case around the operational problems it would solve, the cost, the expected impact, and how we would transition the team into the new process.
I then supported the rollout by helping define the new workflow and how the team would use the platform moving forward.
Business case and recommendation: I documented the workflow problems, evaluated the operational case for Hootsuite, and outlined how the rollout would reduce manual coordination and support a more scalable approval process.
After implementing Hootsuite in June, coordinator time spent on posting and scheduling dropped significantly. Average monthly time decreased from 13.8 hours in April-May to 6.1 hours in July-August, a reduction of approximately 56%.
This supported the original business case for the platform: reducing manual work and giving the team more time to focus on higher-value activities.
Wispr Flow was a different kind of technology rollout. Instead of replacing an existing platform, the goal was to introduce an AI tool that could make everyday work faster and easier.
I evaluated where it could realistically help the team, introduced the tool, shared practical use cases, and supported adoption as people began incorporating it into their day-to-day work.
The focus was on making AI useful and approachable rather than introducing technology just for the sake of using AI.
Pilot kickoff and guardrails: I introduced the tool, explained where it could help, set expectations for responsible use, and gave the team a practical starting point for testing it in their day-to-day work.
Team quick-start guide: After the kickoff, I created this one-page reference so the team could start using Wispr Flow right away.
The initial focus was getting the pilot up and running. I gave the team a clear starting point, shared use cases that fit their day-to-day work, and documented guidance they could refer back to after the kickoff. I did not have enough post-rollout data to claim a quantified productivity impact, but the pilot created a structured way to test whether the tool was useful before considering broader adoption.