Strategy
Projects
Click project links below to learn more.
​
01 Compliance Maturity Model
An example of how I leverage frameworks to bring clarity in ambiguous situations
​
An example of how I approach strategic communication objectives to influence key stakeholders
​
03 Dependency Dashboard Strategy
An example of how I approach developing insightful visualizations in ambiguous situation
​
Are you more interested in how I operationalize initiatives? Visit my Operations Projects page.
Interested in connecting? I have you covered! Let's connect via email or LinkedIn.
01 Compliance Maturity Model
Summary
AT&T's Chief Compliance Office (CCO) was interested in defining success and effectiveness for the organization in an environment where “reactive compliance” was an industry standard
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Key Stakeholders
-
Chief Compliance Office Leads and Leadership
​
Challenges
-
Success varied by Compliance program
-
Limited external research and examples
-
Siloed organization
-
Flexibility in logic
-
Impacts to existing program processes
​
Approach / Solutions
-
Internal and external investigation. Leveraged external and internal resources to develop the initial structure
-
Stakeholder management. Reviewed framework with program leads and executive leadership
-
Conceptual visuals. Developed visuals to illustrate the organization's ability to compare progress across entities
​
Results
​​
​
​
​
​
​
​
​
​
​
​
-
Maturity model framework was presented to the former AT&T CEO by the Chief Compliance Officer and approved
-
Framework was integrated with the business unit programmatic risk assessments
Initial attempt to capture my thoughts and questions around the definition of "success" and "effectiveness" as it relates to compliance.
Map of key questions that supports each category in a quantitative or qualitative way.
Taking the key components of an effective compliance organization to help illustrate the areas of focus of the maturity model.
Initial attempt to capture my thoughts and questions around the definition of "success" and "effectiveness" as it relates to compliance.
02 Leadership Personas
Summary
AT&T's Design Technology was interested in a mechanism to educate the organization on key stakeholders and their respective business goals to help create design deliverables that resonated with the business
Key Stakeholders
-
Design Technology Leadership
-
Design Operations
-
All Disciplines (e.g., Design, Research, Tech, Content, Program Managers)
​
Challenges
-
There are 50+ stakeholders per program
-
Leadership strategic priorities are not centrally located
-
End user of design deliverables are actively being defined
​
Approach / Solutions
-
Research and discovery. Met with program leads to map known stakeholders and roles
-
Prototype development. Developed initial prototype and solicited feedback from end users
-
Iterative approach. To accommodate the ‘unknowns’, an iterative approach was taken to keep the document relevent
-
Communication. Educated end users and leadership on the intent
​
​
​
​
​
​
​
​
​
​
Results
-
The Leadership Personas document was used as a reference guide for future programs to drive better understanding of the team's stakeholders prior to the design kickoff
03 Dependency Dashboard Strategy
Summary
AT&T's Transformation Office (TO) PMO Dependency Strategy was interested in a dashboard that provided a holistic cross-functional view of dependencies that would impact program’s ability to achieve the $6B+ in financial benefits over a 3-year span
​
Key Stakeholders
-
TO PMO Leads
-
TO Execution Leads
-
Finance
-
Business Unit Development Lead
​
Challenges
-
Understanding the problem statement
-
Assigning value to dependencies
-
Minimizing administrative efforts for the users
​
Approach / Solutions
-
Use case development. Drove the identification of use cases for the dashboard
-
Prototype testing. Drafted dashboard concept and solicited feedback
-
Communication. Developed and executed communication plan
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Results
-
Dashboard was used to track and monitor dependencies across the program by the key stakeholders
Partnering with the Dependency team lead and end users to understand the desired insights and use cases for each view
Low fidelity version of the Dependency dashboard that was used to get buy-in from key stakeholders without utilizing development resources
Partnering with the Dependency team lead and end users to understand the desired insights and use cases for each view