Method overview
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Method overview

  • 613 views
Uploaded on

Method to use for GTN project

Method to use for GTN project

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
613
On Slideshare
613
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
14
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • This module will introduce different concepts. These concepts will be explained in detail, however, it is important to understand the ideas behind these concepts.PersonasScenariosReference model, also referred to as the reference architecture
  • Slide Objective:Introduce how we will use scenarios and personas to help define and overall solution.Personas, identify a specific type of user by creating a fictional person with considerable biographical details--a given name, gender, age, education, interests, work description, and even a photograph or idiosyncratic element - to bring the Persona to life so that they stick in the mind. The Persona description identifies both the goals of the fictional person and the goals of your enterprise for such a person. It should include the skills, the tools, and the working environment of the Persona, especially when these details will affect the interactions and transactions between persona and enterprise (usually through a website).Creating Personas is related to but should not be confused with traditional market segmentation, where typical customers are identified for targeting sales messages. Personas are created from user research - interviews, often in the field, with real users - by clustering the characteristics of important representative users into archetypal characters. The aim is to include all important user characteristics in at least one of the personas. For example, if some users work on Macintosh, at least one Persona should be a Mac user.The Persona is used by information and interaction designers to help imagine how a real user will react to their designs. Each Persona has clear needs or goals that help the designers look at the project from a point of view different from their own. Many design failures are traceable to designers (or programmers) who unconsciously assume their users are like themselves.The Persona also allows a sort of virtual user testing, before getting to the real user testing phase. When Personas are really working, designers and programmers talk as if they are real people, people that they know well.
  • A scenario describes the way a daily activity will be executed in the future, as soon as required tools are in place and as soon as the end users are willing and able to start working with the scenarios. The Scenario describes:the benefits for the business and the end user. the skills required for the end user in order to be able to work successfully within the scenario.Required IT solutions (hardware devices / software / tooling)Rules of Engagement: Scenarios can only be successful when all participants stick to a defined set of rules of engagement.
  • This version of the Reference Model is used in discussions with the Business Decision makers. It show domains, but only on a high level functionality level. This workshop will explain the technical version of the same model, which can be used in the translation of functional requirements into a profound technical solution.
  • Slide objective: Highlight Persona definition.Personas are being used to identify different user segments within an organization, and to determine what the Persona’s specific needs and challenges are. It will help the organization in the design of a workplace that closely fits the needs of the individual end user, while safeguarding a sufficient level of standardization.
  • Slide Objective: Explain the combination of characteristics that will determine the different Persona types.
  • Slide Objective: Explain how a Persona is described. The Persona always contains a general description which will give the Persona a personal flavor. It contains a ranking on the three different characteristics (discussed in the previous slide); showing the Persona’s level of mobility, autonomy, and collaborative behavior. It contains a graph showing the relative weight of the Persona, compared to other Persona types. The willingness to innovate: it is important to know whether a specific Persona is willing to innovate at an early stage, or is more reluctant in adopting new ways of working. This helps in determining the deployment roadmap. It explains the different bottlenecks and challenges that each Persona runs into. It shows the current appreciation of the way he is supported in his daily activitiesIt shows the Persona’s required hardware profile. Note that all other items reflects the current shape the Persona is in.Explain that these different information elements will be explained in more detail later.
  • Slide Objective: This slide shows four different Persona types. Karim – the call center employee. Karim is a typical task worker, always working at the same office and working according to strict procedures and guidelines. Johan – the project manager, always working from the same office. He determines, to a large extent, the way how and when he does his work.Renate – a mobile worker in an executive position. She is a person who depends on the people within her team. Mario – the sales person, most of the time working on his own at the customer. He has full control over his own calendar. Additional tools and technology would be very beneficial for him, but he the type of person who is used to doing things his own way and is not too open for new ways of working.BuildEach Persona represents a percentage of the total workforce. This percentage is important in determining your deployment strategy.
  • Instructions for this slide:Step 1: Discuss the mobility aspects of the current workforce (that is - does everybody work on one location or from different branch offices). Do people work from home or at customer’s site? Explain how mobility is changing and how it impacts the need for tools that support the mobile worker.Step 2: Explain why the autonomy axis is important to take into account. People who are working completely autonomous will by nature be more depending on productivity tools. The non-autonomous worker will be using LoB-apps most of the time; no further input required from the customer.Step 3: Explain that a Contractor is not a separate Persona. Depending on the customer, a contractor can be any Persona. Regarding the contractor, it is important to start the discussion on how the customers wants to serve contractors (Will the be getting their equipment from the customer? Will contractor be supposed to bring their own devices? What measures needs to be taken in case the contractor brings his own device?)Since Personas – at first sight – can be experienced as being too abstract, it is important to give examples of function types within a Persona. This slide contains generic examples.
  • It will not always be possible to map all employees into a Persona. There may be special requirements for specific function types or persons. These need to be taken into account. Based on these special requirements, it may be necessary to define an additional Persona. However this should be decided carefully. The amount of Personas should be kept as minimal as possible. Not every exception should lead to a different workplace implementation.
  • Slide Objective: The purpose of this exercise is to give the customer a better understanding of the Personas. It is important to note that a Persona shouldn’t be mixed up with a function type. Multiple function types may apply to one Persona. On the other hand: a specific function type can appear in different Personas (For example, a mobile and a non-mobile project manager; this depends on the type of customer but may also depend on the end-users own mobility preferences).
  • Slide Objective: Special requirements which will influence the technology profile of the different Personas.Requirements you can think of are: special performance requirements, compliance requirements, VIP support, and others.Be careful on how to treat exceptions. Not all exceptions should lead to an additional Persona.
  • Slide Objective: Review Persona distributionsIt is important to get a feeling on the division of the personas over the workforce. This information should be collected prior to the workshop. In most cases the HR department will be able to provide this information. Note: Office Worker and Mobile Worker and Task Worker and Deskless Worker equals 100 percent20 percent of 100 equals Contractor. It is important to note that the Contractor as such is not a Persona.
  • Slide Objective: This exercise will give insight in the current hardware profiles within in the company. Instruction: Use this slide as well to gather ideas on how the customers vision on future hardware profile and to discuss what profiles may be best for the different Persona types.
  • Slide Objective: Review an example PersonaBuild 0: Click to let the “Persona – an example” text disappear.This slide shows how a Persona is described. We normally see that the Personas are printed (A1) and are shown throughout the building. This will help the end users to identify themselves with a specific Persona type. It will help the IT department communicate what they want to achieve by introducing a new workplace and by managing expectations of the end users.The Persona information, used in this workshop are gathered throughout a large number of so called workforce analysis, executed a customers in different industries. Based on these analysis, we conducted a set of more or less generic Persona types. Please note that tailor made Persona definition normally is done based on a large scale survey at the customer, supplemented by in-depth 1:1 interviews with individual employees. The Personas used in this workshop may not fully apply to your organization.Instructions: Discuss the different elements from the Persona description.Description: This section contains general information on Karim. Personal information like age, marital status, hobbies, and others can be added in order to give the Persona type a more personal touch.Current situation: This section explains Karim’s work style. It also states the percentage of people like Karim within the customer’s organization.Distribution of Personas: This graph contains all customer’s Personas, and shows the distribution of the different Persona types. This graphs help in explaining the relative weight of each persona type.Willingness to innovate: Research shows that not all Persona types by nature have the same ability / willingness to innovate. There a five different categories, varying from “Innovators” to “Laggards” and the indications in between.Karim’s current profile: this picture represents the Persona’s scores on Mobility, Autonomy, and Collaboration. Karim has a relatively low score on Mobility and Collaboration needs. His autonomy in his daily job is minimal. This means that the way he does his job and the activities per day, are determined for him.
  • Slide Objective: Further review of Persona typeOpportunity:This section contains the most important opportunity for this Persona type. The information is derived from interviews with employees in this Persona type. Solution: This section describes the most important technical solutions, as stated by people in this Persona type.Benefits: This section contains examples of business benefits. Bottlenecks and facts: This section contains the most important constraints and barriers that the Persona faces in his daily work. Rating current activities: This section explains how the Persona type rates the current IT support in execution of different tasks.Hardware profile: It shows the Persona’s required hardware profile. Note that all other items reflects the current shape the Persona is in.
  • As explained before: A scenario describes the way an activity can be executed in the future, using new technology. In the next slides, the purpose, benefits, and anatomy of a scenario will be explained.
  • Slide Objective: Explain scenarios.Scenario description: The scenario always contains a description, explaining what the scenario is about and how the scenario may make “life easier” for the scenario-users.Story board: The storyboard is used to give insight on how the different tasks within the scenario are executed, explains the context of the scenario, and the relation between the different tasks.Required Cultural and behavioral changes: It is our experience that introduction of new technology also requires changes in the way people behave and in and organization’s cultural aspects. These aspects are explained in this section.Business benefits: What benefits may the organization expect from the introduction the this scenario.Skills: What technical skills does a person need in order to be successful in using the scenario.IT capabilities: What IT capabilities need to be in place, in order to be able to use the scenario.Rules of engagement: Without agreement on how people will work with this scenario, the scenario will fail. In many cases people start working in a more virtual setting. This reinforces the need on clear rules of engagement.
  • Slide Objective: Discuss detail of scenariosWe now will discuss a few scenarios in detail. There are technical and functional scenarios along with generic and customer-specific scenarios. During this workshop we will discuss the functional scenario “smart meetings” and the technical scenario “anyplace, anywhere”.These are typical examples of generic scenarios, relevant to most of our customers. When required, we can help you describe scenarios, specific for your organization.
  • Now we have introduced the different services, we will introduce the Microsoft reference model, or the reference architecture.This model will help translating the functional requirements into the technical solution.There are two different representations of the model, each with a different target audience.The Business: Explaining the different types of high level functionality. This helps explaining why implementation of certain end user functionality may require implementing additional data center services.IT staff: Covering the detailed description of capabilities and workloads, relevant for the different domains.The concept of Capabilities and Workloads will be explained on the following slides.
  • This slide is included to help stimulatefurther discussion if required.

Transcript

  • 1. Module Overview
    Users / Personas / Scenarios / Reference Model
  • 2. Optimized Desktop Strategy
    Infrastructure Strategy
    Scenarios, Workloads and Capabilities
    1
    2
    3
    4
    Personas
    Distribution
    Strategy
    Managed Client
    Virtual Desktop
    Infrastructure (VDI)
    or Blade PC
    TS Remote
    Client
    Virtualized
    Applications
    Rich Client
  • 3. Important Concepts Explained
    Personas
    Personas are archetype users which represents a group of employees within the organization.
    Each Persona has a distinct set of characteristics.
  • 4. Important Concepts Explained
    Scenario
    A Scenario describes the way an activity can be executed in the future, using new technology.
  • 5. Important Concepts Explained
    Reference Model
    The Reference Model helps in translating the end users requirements into the appropriate technical solution.
  • 6. Personas
  • 7. Optimized Desktop Strategy
    Infrastructure Strategy
    Scenarios, Workloads and Capabilities
    1
    2
    3
    4
    Personas
    Distribution
    Strategy
    Managed Client
    VDI or
    Blade PC
    TS Remote
    Client
    Virtualized
    Applications
    Rich Client
  • 8. Persona definition
    Personas are archetype users which represents a group of employees within the organization.
    Each Persona has a distinct set of characteristics.
  • 9. Persona Characteristics
    High
    Low
    Autonomy
    • Level of autonomy in the daily routines
    Bound to procedures and guidelines
    High level of flexibility
    High
    Collaboration Needs
    • Percent of time working on a team
    • 10. Frequency of collaboration tool use
    • 11. Geographic distribution
    • 12. Managing document versions
    Low
    Collaboration leader with three or more teams
    Task worker, no project-based teams
    High
    Low
    Mobility
    • Where is the job executed?
    • 13. What devices are being used?
    • 14. What’s the Persona’s attitude towards working anywhere/anytime
    Mobile, connected, and working everywhere
    Desk-bound or deskless
  • 15. Persona’s current profile
    Description
    Opportunities
    Challenges and facts
    Solution
    Benefits
    Current appreciation
    Innovation adoption behavior
    Persona Anatomy
  • 16. Contoso Company Persona Type Overview
    KARIM JOHAN
    20 percent
    60 percent
    RENATE MARIO
    10 percent
    5 percent
  • 17. Segment Workforce in Personas in Four Steps
    1. How mobile is this user?
    3. Begin placing user types
    2. How much PC usage autonomy does this user have?
    Great deal of autonomy and control over applications and data
    Mobile Workers
    Senior Executive
    Business Consultant
    Field SalesRepresentative
    Office Workers
    Highly independentconnected workers
    Contractor
    Single, alwaysconnected location
    Highly mobile, worksboth offline and online
    Task Workers
    Bank Teller
    Call Center Associate
    Deskless Workers
    Retail Associate
    Nurse
    ManufacturingFloor Manager
    Very little autonomy and control over applications and data
  • 18. Segment Workforce in Personas in Four Steps
    Step Four. Consider Special Requirements for Some Users
    But some have specialcompliance requirements
    Office Worker with SpecialRequirements
    Financial Trader
    Government Worker
    Contractor
    Office Workers
    Highly independentconnected workers
    Mainstream Office Worker
    Engineer
    Designer
    Architect
    All have high autonomy andare always connected
    Compliance
    Productivity
  • 19. Exercise One: Map your Function Types on Personas
    Mobile Workers
    ….
    Office Workers

    Contractor
    • …..
    Task Workers
    ….
    Deskless Workers
    …..
  • 20. Exercise Two: Special Requirements
    Mobile Workers
    ….
    Office Workers

    Contractor
    • …..
    Task Workers
    ….
    Deskless Workers
    …..
  • 21. Exercise Three: Persona Distribution
    Mobile Workers
    10 percent
    Office Workers
    25 percent
    Contractor
    • 20 percent
    Task Workers
    50 percent
    Deskless Workers
    15 percent
  • 22. Exercise Four: Persona Hardware Profile
    Mobile Workers
    Laptop / tablet
    Softphone
    Smartphone
    Office Workers
    Desktop
    Softphone
    Smartphone
    Contractor
    ???
    Task Workers
    Thin Client
    Softphone
    Deskless Workers
    Slate
    Smartphone
  • 23. Task Worker
    Description:
    For Karim, technology is simply an means to an end. Karim is able to work independent from other colleagues. He works from 9 to 5. He works according predefined procedures and guidelines and isn't actively involved in optimizing his work. In order to change the way Karim works, his way of thinking needs to be changed first.
    KARIM
    Current Situation
    Non mobile task worker. This Persona-type represents 60 % of the total number of employees. Their daily activities are highly repetitive. To a large extend the process information in stead of producing it.
    Office worker
    Karim’s Current Profile
    • Mobility Low High
    • 24. Autonomy Low High
    • 25. Collaboration Low High
    Personas – an example
    Distribution of Personas
    Task Worker
    Deskless worker
    Mobile Worker
    Willingness to Innovate
  • 26. Task Worker
    Bottlenecks and Facts
    “For reasons unknown you are not authorized to access relevant information”
    OPPORTUNITY
    It is Karim’s experience that Telecommuting brings increased productivity. The current state of technology doesn’t support it.
    WORKPLACE
    Solution
    Benefits
    • EfficiencyFocus on effective execution of key activities by administrative staff instead of secondary activities.
    • 27. Reduced costsReduce paper consumption (including print agendas) and the cost of finding information. "Policy conditions? I had to find them on the public internet!”
    • 28. Employee satisfactionAdministrative burden is perceived as interfering.
    • 29. Digitization“At Central Purchasing many contracts and RFP documents are stored, often on paper. Contracts are also still being stored on paper. I am a kind of intermediary between two parties (buyer and supplier)."
    • 30. Communication
    “We don’t have a central facility for Conference calls.”
    “For each project, there is a separate document with contact details."
    Rating current activities
    Working in teams
    Communication and announcements
    Communicating
    Finding people and expertise
    Organizing and executing meeting
    Inter-departmental cooperation
    Collaborating on documents
    Finding documents
    Exchanging confidential information
    .
    Hardware profile
  • 31. User Scenarios
  • 32. Optimized Desktop Strategy
    Infrastructure Strategy
    Scenarios, Workloads and Capabilities
    1
    2
    3
    4
    Personas
    Distribution
    Strategy
    Managed Client
    VDI or
    Blade PC
    TS Remote
    Client
    Virtualized
    Applications
    Rich Client
  • 33. Scenarios Explained
    Scenario description
    The storyboard
    Cultural and behavioral changes
    Rules of engagement
    Required IT resources
    Required end user skills
    Business Benefits explained
  • 34. Smart Meetings
    In four steps you can organize, lead, attend a meeting, allocate the meeting’s actions and store all relevant information in a virtual meeting workspace. This helps all participants to effectively prepare the meeting. All participants will have up to date insight in the meeting’s agenda and will work with up to date documentation. The meeting itself can be joined physically or virtually. In a virtual setting the participants will have voice- and video conferencing capabilities readily available.
    Storyboard
    Initialize a central workspace where all relevant information is stored. This workspace is op to all participants. Participants can add documents, agenda items and others.
    On-flight task allocation and producing meeting minutes.
    Participants will find their tasks in their mailbox. Status is updated in the meeting workspace.
    Invite meeting participants
    A meeting location is arranged. This can both be a physical and virtual location. Not all participants need to physically attend.
    This scenario will help you optimizing your meetings. Tasks, meeting minutes, meeting documents are available at your fingertips. All participants can prepare optimally. The meetings will be more structured and will consume less time. Since the meetings can be attended virtually, you can decide on whether to face the traffic jams or not.
    Collaboration
    Portals
    Workspaces
    Enterprise Search
    Information Access
    Interactive experience and navigation
    Creation of meeting workspaces
    Adding, changing and deleting meeting workspace content.
    Create recurring meetings, using Outlook.
    Creating tasks and alerts in Outlook.
    Increased efficiency; shorter meetings.
    Increased transparency
    Relevant information stored centrally, accessible for the right people.
    Accelerated decision making, based on up to date information.
    Respect people’s time.
    When attending a meeting, be prepared.
    Keep your electronic calendar up to date. Make your calendar accessible for your colleagues.
    Use the meeting workspace to find and share documentation and information.
  • 35. Microsoft Reference Model
  • 36. Distribution Strategy
  • 37. Optimized Desktop Strategy
    Infrastructure Strategy
    Scenarios, Workloads, and Capabilities
    1
    2
    3
    4
    Personas
    Distribution
    Strategy
    Managed Client
    VDI or
    Blade computer
    TS Remote
    Client
    Virtualized
    Applications
    Rich Client
  • 38. At this point you may want to use the “Windows Optimized Desktop Solution Accelerator” to provide further analysis of user profiles.
    This is not required however it is important to take the user personas and directly map their requirements to technology solutions. For example a task worker may require a virtual desktop infrastructure (VDI) solution while a mobile worker requires a rich client.
    The following slide is an output of the solution accelerator.
    Notes (hidden) – Scenario Template
  • 39. Distribution Strategy Mapping
  • 40. Mapping Distribution Strategy to User
    Location
    Employee
    Stationary
    Home
    Flexible
    Applications
    Complex
    Limited
    Laptop
    Desktop
    VDI
    Employee Owned(Remote VDI)
    Retail Branch Offices
    Back Office
    Contact Centers
    Analysts
    Finance
    Office and Mobile Workers
  • 41. Infrastructure
  • 42. Optimized Desktop Strategy
    Infrastructure Strategy
    Scenarios, Workloads, and Capabilities
    1
    2
    3
    4
    Personas
    Distribution
    Strategy
    Managed Client
    VDI or
    Blade computer
    TS Remote
    Client
    Virtualized
    Applications
    Rich Client
  • 43. This material is provided for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED.
    The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, places, or events is intended or should be inferred