Delivery Documentaries are a behind the scenes look at how our Enterprise Architects (EAs) in the field perform Value Realization activities for customers. They are raw and real, and the purpose is to share what actually happens on the ground. They are always a learning opportunity, and we hope that over time we can help bridge the state of the art with the state of the practice, and continue to move the ball forward.
In this engagement, an Enterprise Architect supported a hospital facing challenges related to having no strategy for supporting user devices, as the devices rapidly proliferated among the staff.
The EA helped the hospital identify an actionable strategy, educate stakeholders about mobility issues, provide a strategic direction, and introduce a framework for addressing mobility. During the engagement, the EA worked primarily on-site, and with the close support of the engagement manager, services executive (SE), and account technology strategist (ATS).
During the engagement, the EA met with primary and secondary stakeholders to perform assessments, performed research into mobile strategies using existing IP and personal contacts, and created a deliverable that contained key findings for a mobility strategy, recommendations, trends, adoption frameworks, and best practices.
Contoso Hospital was having pre-sales conversations with an account executive (AE), ATS, and SE about the needs of the hospital for a mobile strategy. I began participating because I had experience working with mobility and BYOD (“Bring Your Own Device,” where employees use their own devices to perform work).
I was the point person in the pre-engagement meeting. Our goal for the meeting was to try to understand and scope the engagement. I was joined by the Microsoft delivery excellence director and the account team.
The initial stakeholders were IT decision makers, directors that report to the CIO. We set expectations right from the start about what a strategy is, and what it isn’t. We discussed that the deliverable would lay out priorities and address the issues that the hospital is experiencing now.
We discussed that the deliverable would achieve the following:
We discussed that the deliverable would not:
Over the course of the next two weeks, I visited again with the account team, and did some basic preparation for the engagement while the contracts were signed and the sales motion finalized.
The heart of the kickoff was level setting. During the kickoff, I communicate the following to the stakeholders:
I began working full-time on-site, finding it valuable to be close to the stakeholders. I was able to introduce myself, my work, and my associates. My account team also helped with appropriate introductions.
My engagement manager and account technology strategist attended assessment and planning meetings. They helped provide insight and ensure that we were working towards the goals of the engagement.
When I began working on the deliverable, I had a sense of the stakeholder priorities from the prior meetings, but to identify more details I needed to conduct a wider stakeholder assessment. I decided to use personas as a cornerstone for developing strategy, and for communicating about mobility tools and scenarios.
Following guidance from the key stakeholders, I identified primary, secondary, and additional stakeholders with which to perform assessments. I met stakeholders, learned about their roles, interests, and stakes in the mobility initiatives. For example: how mobility affected their activities, what they saw as the main issues and valuable opportunities, and the look of success.
I then started developing a BYOD strategy for the hospital. I accessed many resources during my research. Here are some examples of the resources I used:
In the final deliverable, I aimed to provide a focused collection of items for the hospital to explore. Here is a list of some of what I identified:
My final deliverable for Contoso Hospital was a presentation supported with a slide deck that included the following topics:
Is there more the story?
You bet.
This was only the beginning.