SlideShare a Scribd company logo
09 Reacting to change and product evolution
09 Reacting to change and product evolution
09 Reacting to change and product evolution

More Related Content

PPTX
Four step adoption plan for Office 365
PPTX
05 Define and prioritise solutions
PPTX
03 Executive sponsorship
PPTX
BRK2016 Driving Yammer adoption
PPTX
00 Overview of our adoption plan
PPTX
07 Adoption plan guide
PPTX
BRK2099 Creating opportunities through Office 365
PPTX
Office 365 - Teams, what to use when
Four step adoption plan for Office 365
05 Define and prioritise solutions
03 Executive sponsorship
BRK2016 Driving Yammer adoption
00 Overview of our adoption plan
07 Adoption plan guide
BRK2099 Creating opportunities through Office 365
Office 365 - Teams, what to use when

Recently uploaded (20)

PDF
Microsoft Solutions Partner Drive Digital Transformation with D365.pdf
PDF
Getting Started with Data Integration: FME Form 101
PDF
A novel scalable deep ensemble learning framework for big data classification...
PDF
From MVP to Full-Scale Product A Startup’s Software Journey.pdf
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PPTX
Group 1 Presentation -Planning and Decision Making .pptx
PDF
Assigned Numbers - 2025 - Bluetooth® Document
PDF
project resource management chapter-09.pdf
PDF
Transform Your ITIL® 4 & ITSM Strategy with AI in 2025.pdf
PDF
A comparative analysis of optical character recognition models for extracting...
PDF
Univ-Connecticut-ChatGPT-Presentaion.pdf
PDF
Hybrid model detection and classification of lung cancer
PDF
gpt5_lecture_notes_comprehensive_20250812015547.pdf
PDF
Approach and Philosophy of On baking technology
PDF
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
PDF
DP Operators-handbook-extract for the Mautical Institute
PDF
Encapsulation_ Review paper, used for researhc scholars
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
PDF
Mushroom cultivation and it's methods.pdf
PDF
Building Integrated photovoltaic BIPV_UPV.pdf
Microsoft Solutions Partner Drive Digital Transformation with D365.pdf
Getting Started with Data Integration: FME Form 101
A novel scalable deep ensemble learning framework for big data classification...
From MVP to Full-Scale Product A Startup’s Software Journey.pdf
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
Group 1 Presentation -Planning and Decision Making .pptx
Assigned Numbers - 2025 - Bluetooth® Document
project resource management chapter-09.pdf
Transform Your ITIL® 4 & ITSM Strategy with AI in 2025.pdf
A comparative analysis of optical character recognition models for extracting...
Univ-Connecticut-ChatGPT-Presentaion.pdf
Hybrid model detection and classification of lung cancer
gpt5_lecture_notes_comprehensive_20250812015547.pdf
Approach and Philosophy of On baking technology
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
DP Operators-handbook-extract for the Mautical Institute
Encapsulation_ Review paper, used for researhc scholars
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
Mushroom cultivation and it's methods.pdf
Building Integrated photovoltaic BIPV_UPV.pdf
Ad
Ad

Editor's Notes

  • #3: The super-freighter in the image moves deceptively quickly – it runs on a schedule, it’s movements within controlled shipping areas are published, it will cross the Atlantic in around 10 days though it is slow to start, it takes a long time to change direction and often needs help doing so, normal waves have no impact upon it, icebergs are foreseen and avoided. The containers it carries change regularly and occasionally a “reefer” falls off and is lost at sea. Now consider Office 365 to be the super-freighter, the containers a mix of product features. The service is evergreen – that is Microsoft updates it on a regular cycle. Some of their Roadmap is published (schedule), some of the changes are communicated (published shipping movements), some of the changes are just imposed (with the outcome that some of the containers simply fall overboard), new features are added whilst others are taken away (containers are loaded and others unloaded.) As a consumer, the bulk of this is out of our control. In addition A/B testing can temporarily add / remove functionality for specific users (or in freight terms, a container gets temporarily misplaced when it is unloaded – finding itself in the wrong bonded warehouse). Therefore we have to change our mind-set from “big change projects every x years” to “smaller updates every month”. Our services cannot be super-freighters that take significant time to turn or stop. To stay agile and reactive, we have established our Ships Bridge in yammer and have created an O365 Change and Strategy Group (https://www.yammer.com/mottmac.com/#/threads/inGroup?type=in_group&feedId=5849903) and are trying to #workoutloud. The group contains key stakeholders from across the IT service and we can invite others in as the need arises. The point is that it’s about preparedness, monitoring the channels you have access to, reacting as quickly as you can when something new is unloaded and not fighting the super tanker.
  • #4: We monitor and react to change by:   1. Identifying the potential changes For this we have a network of inquisitive spy’s. We use a combination of the Microsoft Monthly Service Update ‘newsletter’, weekly reviews of the Message Centre, companies that we are working with, a near constant eye on the O365N, the O365 Roadmap and some other sources that we’d not like to reveal. All of the knowledge is discussed in a dedicated Yammer Group and when we know the MSG ID we tag the conversations with it (as well as adding links to threads on the O365N etc.). We also maintain a tracking spreadsheet (as you’ve got to have a spreadsheet). To be honest it is too much like hard work and Yammer and Microsoft should make this easier.   2. Discuss the potential changes We have an allocated slot in our weekly team meetings to discuss roadmap items and how we intend to tackle them. The tricky part is not knowing exactly when the change will arrive. I usually take actions to try and get more information. For example, Yammer announcements are usually pretty light on actual detail. What really helps is the Change Alerts (https://www.yammer.com/itpronetwork/#/threads/inGroup?type=in_group&feedId=4355152) group in the O365N as customers typically in North America get the change days or weeks before it arrives in our tenant. By following that group, we get an early warning of impact, mitigation and customers we can talk to. Occasionally Microsoft will retire a product as part of a change and so it is important to understand the Support Lifecycle https://support.microsoft.com/en-gb/lifecycle   3. Test the change Fingers crossed it arrives in our First Release tenant. At that point we play and test it, grab screenshots and prepare the communications. Each element of O365 has a dedicated space in our new Intranet. We typically prepare a new page that describes the feature and briefly explains how staff might use it. Massive exception to the rule is Yammer as from this day to the next we do not know what is A/B and what is feature release.   4. Communicate the change Obviously the greater the impact the more we do. Massive change means staff briefings, board meetings etc. Significant items are then reviewed with projects and/or change tasks created (in ServiceNow). The bulk of changes are communicated using our Intranet – we use the article created in 3 as the news item. We also push news out across yammer – again with links back to the article. Sometimes a targeted email blast is employed and we have a dedicated service alerts banner that we can enable in our intranet.     * As an aside, we operate a second tenant with a small amount of content in full First Release mode and our Production tenant has Selective First Release for named users - sometimes the change is hard to test as we do not have enough content or numbers of users in our test tenant - we are looking at using ShareGate to snapshot our production instance and replicate the content in test, though this will not replicate the number of users which is vital for testing items like people search and profiles