MiVox Project Issue Analysis (Mock Project)
Project goal
Identify and address underlying causes of frequent code issues within the MiVox project to improve code quality and team efficiency. This project was part of an IBM consulting course designed to simulate real-world scenarios with difficult stakeholders, sharpening my consulting and stakeholder management skills.
What I did
– Read/understand Brief
– User Interviews with Stakeholders and Developers
– Gathered Insights
– Ideation on Solution
– Defined Solutions
– Deck Creation for Solution Pitch
– Presented to Stakeholders
Outcome
– Course leader’s Buy-in: Successfully convinced course leaders to adopt my proposed solution, demonstrating the effectiveness of my approach in addressing the identified code issues.
– Improved Team Collaboration: Regular reviews and workshops promoted teamwork, helping manage stakeholder expectations.
– Refined Consulting Skills: This simulation helped develop critical skills in handling challenging stakeholder interactions, building consensus, and presenting solutions with empathy and clarity.
The detail
Reading Brief
Understanding the Scope: Analysed the project brief to establish the context, coding standards, and initial problem areas. Recognising the simulation aspect, I focused on preparing to navigate stakeholder expectations and handle potential resistance.
Setting Objectives: Defined objectives to improve coding practices, reduce redundancy, and enhance workflow efficiency, with a focus on demonstrating consultative problem-solving skills.
User Interviews with Stakeholders and Developers
Engagement with Key Players: Conducted interviews with simulated stakeholders and developers, practising active listening and managing difficult conversations.
Uncovering Core Issues: Identified common concerns such as lack of familiarity with coding standards, inconsistent practices, and minimal peer review processes. Navigated complex stakeholder dynamics by empathising with their priorities and concerns.
Gathered Insights/Ideation
Analysing Feedback and Identifying Gaps: Organised data from interviews to identify recurring issues, practising diplomacy and assertiveness in managing conflicting perspectives from stakeholders. Recognised that limited knowledge and lack of process enforcement were key challenges, and aligned these insights with stakeholders’ interests to gain their support.
Brainstorming and Prioritising Solutions: Explored potential solutions, including peer reviews, coding workshops, and agile practices, while considering stakeholder concerns. Prioritised cost-effective, high-impact actions that balanced the needs of both developers and challenging stakeholders.
Defined Solutions
Deck Creation for Solution Pitch
Building the Deck: Created a clear, compelling deck to communicate the problem-solution path effectively, anticipating potential pushback from stakeholders.
Highlighting ROI: Demonstrated the benefits of the solutions, including improved code quality and productivity, with zero additional costs—emphasising benefits stakeholders cared about.
Outcome/Feedback
Delivering the Pitch: Presented to a panel simulating challenging stakeholders, honing my ability to handle objections, clarify misunderstandings, and maintain professionalism under pressure.
Securing Buy-In: Successfully gained stakeholder approval by addressing concerns proactively and aligning solutions with their priorities.
