8 steps to retrieve a lost SharePoint document

SPdocgone-header2We frequently get calls from colleagues whose documents have “disappeared” from their SharePoint site. Over time, we have come up with a few steps to investigate and (often) find them.

They are comparable with the steps taken when you misplace a OneDrive document, but finding lost documents in SharePoint is a bit more complicated than finding them in OneDrive:

  • Other people can edit or delete documents
  • You only have 1 OneDrive (which is one document library), but you probably work in multiple document libraries in multiple SharePoint sites
  • Permissions can vary within and across sites

On the plus side, there is a Site Owner and a SharePoint admin who may be able to help you out!

What could have happened?

These are the most frequent “disappearing acts” of documents:

  • Deleted (deleting a synced folder without disconnecting it first also deletes the documents from SharePoint!)
  • Renamed
  • Moved to another folder in the same document library
  • Moved to another library in the site
  • Moved to another site. This means the original document has been deleted.
  • Moved to your OneDrive
  • Permissions have changed and you no longer have access
  • Metadata have changed so it appears in a different view than usual

Which tools are available?

  • Search
  • Recycle bin
  • The document details pane
  • The site owner or your SharePoint admin

Where to start?

Just like my post about the disappeared web parts and lost documents on OneDrive, I have thought about the best possible order to use the available tools. It may appear to be fastest if you go to the Recycle Bin first, but that may be quite a chore if your site is active, your document has been deleted some time ago and/or document name, the author or the suspected deleter starts with M or N. Sadly you can only Sort, and not Search, in the Recycle bin.

My suggestion would be to first try and find the document in the original library. But please, feel free to disagree! It also depends…:)

1. Search in the Document Library where it used to live

Found it? Open it to see whether this is the document you are looking for. It has most likely been moved from one folder to another, or metadata has changed so it appears in a different view. Take step 2 to find the location if you do not see it straight away and/or confirm with step 7 to see what exactly has happened if you are curious.

SPdocgone-searchlibrary
There are two documents in this library. You can click to open them from there or click “Show more results”

No luck? Move on!

2. Search in the SharePoint site

You can easily do this by clicking “Expand search to all items in this site” on the bottom of the Search results page from step 1.

SPdocgone-searchlibrary2
You do not get any more results in this case, nor the exact location of your documents, but this view allows you to expand search and that will give you more info.
SPdocgone-searchlibrary3
So there is another result if you search in the site. If you get too many results, you may want to use the Files tab and/or the Filters to narrow down. And…this view will show you the path of the document!

Found it? Note down the path and navigate to it to confirm this is the correct document. The document has been moved to another library. Confirm with step 7 if you feel the need.

No luck? Move on!

After this, you can do what is most easy for you.

3. Search from the SharePoint landing page

Found it? Well you are lucky! Unless your document has a very unique name, it will be hard to find between all the other documents in your organization. (Of course, using the Files tab and the Filters should help a little). So, it has been moved to another site. Note down the path and confirm it is the correct document. Confirm with step 7.

SPdocgone-spsearch
Results from SharePoint search. In this case you get results from all of SharePoint, so it will be necessary to narrow down the results by using the Files tab and the Filters. You see there is also a result from OneDrive.

Results from OneDrive are also shown in SharePoint search, so if you have accidentally moved the document to OneDrive, you will find it there as well. Unless you want to know WHEN you did this, there’s no need to confirm with step 7 as you are the only one who could have done this. 🙂

No luck? It has probably been deleted, renamed or had its permissions changed (with or without moving). Take any of the next steps to find out.

4. Search in Office365

Frankly, chances are slim that you will find it here but you can try! If it is not in OneDrive and not in SharePoint (including Teams) it may be in Outlook or Yammer but would you not remember if you have done that? But, just to be on the safe side, give it a try.

Found it? Congratulations! Now move it back to where it belongs!

No luck? Well, you really did not expect to find it after all your other trials, right? Time to look in the Recycle bin.

5. Check the Recycle bin

Found it? Restore it.

No luck? Move on!

6. Ask the site owner if they know, or to search in Library or Site

Found it? It has probably moved to a place to where you do not have access, or you have actively been removed from the access group. Discuss with the site owner to give you access again, if possible.

No luck? Move on.

7. Check the Document Library’s details pane

In some cases you may want to do this earlier, but especially in a busy SharePoint site you need to scroll a lot! If someone knows a good way to export the data into a nice Excel file or something, please let me know.

The details pane is context-sensitive and will display different details depending whether you are on the document library landing page or in a folder.

DisappearedDocs-infopane
Nice icons, clear descriptions and clickable links for documents that are still in this folder or library. Deleted documents are not clickable.

Found it? Confirm it is the correct document and note down the path and/or new name.

No luck? There is one last option…to be done when all else fails.

8. Ask your SharePoint administrator

Your SharePoint admin will likely have permissions to everything so if they can not find the document in Office365 search, it will not exist in its original shape anymore.
Additionally, they can also check the 2nd stage Recycle bin to see if it has been deleted.

Found it in Office365 Search? Confirm it is the document, note down the path and ask the site owner to give you permissions again.
Found it in the 2nd Stage Recycle bin? Ask your SharePoint admin to restore it.
Confirm what has happened with step 7 and give your SharePoint admin a compliment on Yammer or Teams for everyone to see! 🙂

No luck? Sorry….

Any other thoughts?

Did I miss something? Do you think there is a better order? Any other tricks to share? Please let me know!

Image courtesy of ronnieb on Morguefile.com

4 steps to retrieve a lost OneDrive document

onedrivegone-headerWe sometimes get calls from colleagues who have lost a document in their OneDrive. Over time we have learned some procedures to try and find it.
Please be aware that the majority of my colleagues has a F1-license, so I am focusing on OneDrive Online only.

What could have happened?

  • Deleted
  • Renamed
  • Moved to another folder
  • Moved to SharePoint (which means deleted from your OneDrive)

Which tools are available?

  • Search
  • Recycle bin
  • Document details pane

Where to start?

I would suggest to start either with Search or the Recycle bin. I love the details pane, and it has greatly improved since I last wrote about it, but as almost every change is captured, you will have a lot of scrolling to do.

So let’s start with

1. Search in OneDrive

OneDrivegone-search
The search results will show you where the document lives now. If you have many results, use the Filter option top right to narrow down the options. You can filter on modified date, document type and people’s names.

Found it? Phew, that was quick! That means it has been moved to another folder. Confirm it is the correct document and note down the new location. If you want to know WHEN you did this, check out the document details pane. Move the document back to its original folder if the move was an accident.

No luck? Well, there’s other ways to look!

2. Check the Recycle bin

onedrivegone-recyclebin
The search box does not work for the Recycle bin. You can only sort.

Sadly you can only Sort in the Recycle bin, not Search, so if your document’s name starts with M or N, and it has been deleted some time ago, you will have to scroll a great deal.

Found it? Restore it! It will be back into its original folder, but if you forgot which one that was, you can Search again.

No luck? Well, it has been deleted or… it may have been moved to SharePoint more than 93 days ago, so let’s just have a look there.

3. Search on the SharePoint landing page

onedrivegone-sharepoint
You will see where the document has moved to. If you get a lot of results, use the filter option!

Found it? Congratulations! Confirm it is the document you are looking for and remember where it is.

No luck? Most likely you have either deleted the document more than 93 days ago, or renamed the document. There’s only one way to find out!

4. Look in the document details pane

As I mentioned above, you can do this as step 1 or 2 but if you are using your OneDrive intensively, you may need to scroll a lot and the other steps may be quicker.

The details pane has improved a lot since I last wrote about it. It is now available for OneDrive for Business,  has clear icons and displays almost every change. It is context sensitive, so will display different things depending whether you are on your OneDrive landing page or in a folder. It also has clickable links for all documents that are still there. So please use this to check if the document has been renamed and/or moved.
If you have not been able to find the document in another way, this is the one option left. Scroll down until you see a “Deleted” or “Renamed” action for the document in question.

Onedrivegone-detailspane
To create this screenshot, I created a new document from OneDrive, gave it a name, added text in the document, deleted and restored it, and then moved it to another folder. Now you have all the icons and descriptions!

Moving a document to SharePoint only results in a “Deleted” mention, so you have no indication whether it has been moved to SharePoint or just plain deleted.

Found it? Hopefully you renamed it! Click on the title and find out where it lives.

No luck? Sorry, this is all that I can think of…

Can you blame the person with whom you shared the document?

No. If you share the document with someone, they can only edit the text in the document. They can not rename, move or delete the file.

Any other thoughts?

Did I miss something? Do you think there is a better order? Any other tricks to share? Please let me know!

Next time…

…We are going to complicate things by trying to retrieve lost documents from SharePoint!

Picture by ronnieb on Morguefile.

SharePoint Holmes and the Invisible Image

SH-invisible-man-154567_1280The case

“It is possible to show the person’s picture in a list, next to the name?”  the user asked me. “Of course”, I said, but it depends on the list and the definition of the column. Let’s have a look.”

The user did a screenshare with me and showed me the list. It contained a number of “People or Group” columns.

We checked the settings of the columns and it turned out he had used the default option, “Name (with presence)”.

SH-InvisibleImage-Default
The default option when you create a “Group or Person” column.

So I showed him there were more options and that he’d better select “Name (with picture and details)”.

SH-InvisibleImage-Namepicdetails
I suggested this option to make the picture show in the list

So he did, and he went back to the list. But no image was shown.

SH-InvisibleImage-ListModern
No image next to the name 😦

The investigation

  1. I checked the column again, as this was unexpected behaviour. Yes, that was the right setting.
  2. I also tried the other options, “Picture only” in various formats. But the image would not show.
  3. I was flabbergasted. Microsoft Office, especially in the Modern fashion, has such an obsession about pictures, images, icons and other visuals that I could not understand why the picture would not show up. I mean, I have to look at myself all day but SharePoint would refuse this?
  4. But then I thought, what about Classic View?

The solution

I switched to Classic View and there it was:

SH-InvisibleImage-Listclassic
This was what the user was looking for!

The user was happy and changed the Advanced Settings to make sure this list would always open in Classic View for all the site’s users.

I am not so happy, however. This was a modern site with a modern list and a perfectly legit column setting. Why is the picture not displayed in the Modern View, knowing the emphasis Microsoft places on visuals?
Please note it is the same with Styles and Totals – they only display in Classic View 😦
I have already added a warning to my SharePoint Style Counsel blog…

Additionally, over time I have grown an aversion to the Classic view as I think it looks cluttered.

So, does anyone know when can we expect these display options to be available in the Modern view?

About SharePoint Holmes:
Part of my role is solving user issues. Sometimes they are so common that I have a standard response, but sometimes I need to do some sleuthing to understand and solve it.
As many of my readers are in a similar position, I thought I’d introduce SharePoint Holmes, SharePoint investigator, who will go through a few cases while working out loud.

Image courtesy of OpenClipArtVectors on Pixabay

Reaching beyond the usual suspects

IntranetNowBlogheaderOn October 5 I participated in IntranetNow in London. I presented there, and thought it would be nice to create a write-up in my blog, with some images from my presentation. If you prefer the PowerPoint variety, please check out my presentation on the IntranetNow SlideShare.

What brought this on?

Recently we introduced a new intranet (Publishing and team sites) to the organization.

Blog-changes
A overview of the old (left) and the new situation (right). Lots of changes!

We went from a SharePoint 2007 environment on-prem, to SharePoint Online in the cloud. That alone was a big change.

Our old platform was created 10 years before, when the organization was still very decentralized, and people could do on the platform whatever they wanted (which they did) as long as they did not break it (which they did…sometimes 🙂 ).
The new intranet is strictly governed, as there is now a strong central Security and Compliance team, strong Enterprise Architecture, many Governance Boards and Steering Committees and of course our new landlord Microsoft, and they all tell us what people can do and what not.

Additionally, we went from being one large company to two companies and we reorganized as well.

Challenges

We knew we were going to make a big change, so we secured the help of our “usual suspects”, a small group of people active on Yammer, and a small group of active content owners. They kindly agreed to be our Champions, helping us launch the new intranet to their circles of influence.

However, many of them left the organization during the project, or moved to another job, due to the reorganizations. So we were left with an even smaller group of “usual suspects”.

We tried to make up for it by increasing the communications:

  • Yammer messages and YamJams
  • News articles and Newsletters
  • Webinars with demos and question time
  • Local sessions to inform people
  • Emails to site owners
  • Creating training

But well, you know how it goes:

  • People do not always read or act upon communications
  • People only learn when they have a need, so many people left the learning until they had their new intranet and their new site(s).

So despite our efforts, this is more or less how people reacted when they saw their new tools for the first time:

Chaos wallpaper2.png
Sadly I do not know the creator of this wonderful image, but I have used it anyway since it is the best I could find to depict the response of the audience…

People were confused, did not know where to find their content, how to manage their sites, how to navigate, etc.

Action needed!

Well, if you want to implement a new effective digital workplace, this may not be the best response. So we introduced a new role into the organization: the Adoption Consultant. It is their role to make sure that employees

  • know what the DW is,
  • can use it to their advantage
  • and like it, so they will promote it and help others use it

Within this organization, the DW consists of the Office 365 suite plus a few other tools available for all employees.

So we are currently embedding this process into the organization:

Blog-cycle
The Process
  • There is a UX manager who runs a survey with 1/12 of employees every month, asking for user feedback about all IT tools and services.
    There are other sources for feedback (Yammer, support tickets, etc.) but the survey is the most formal one.
  • He turns the responses into usable data and insights.
  • If something relates to the Digital Workplace, he asks the Adoption Consultants to help with it. They determine which remediation actions need to be taken.
    New functionality will also be handled by the Adoption Consultants, as some projects have the objective to “get the software installed on people’s machines” without thinking beyond that point…
    So they think about whether extensive communication and training sessions are needed, or if a link to the help materials of the vendor is sufficient, or anything in between.
  • By implementing those actions it is expected that the complaints and remarks about this topic will be reduced.

Yeah, interesting picture, but what does that mean in practice?

Users: “I can not find anything on the intranet”

UX Manager: “We have found that “I can not find anything on the intranet” is in the Top 3 of complaints for the past months. Adoption Consultants, would you please look into this”?

Adoption Consultants:  “What does it mean exactly, “I can not find information on the intranet”? Do people not know how to search? Are they looking for information that is not there? Do they not know how to navigate?”
* arrange interviews with a selection of complainers*

Adoption Consultant: After some discussions I think

  • We will need to create a campaign to inform people about the options available in Search.
  • We need to suggest to this department that they properly archive their outdated procedures and provide more meaningful and descriptive titles and tagging for their current content.
  • We need to discuss federating SharePoint Search, as some people appear to be looking for content which lives in our IT service system.

What else have we done so far?

  • We have given “Digital Workplace roadshows” in various locations across the world, explaining what the Digital Workplace is and how people can best use it. These have been received really well.
  • We have started a campaign about the different options of Search, update your profile, etc.
  • We manage a “Digital Workplace” group on Yammer as THE place for discussion. This is really well-used and popular.
  • We have created procedures to communicate consistently about projects that bring new functionality to the organization, using consistent channels (such as that Yammer group).
  • We are working with local focal points as they know more about their specific situation.

What are the results?

As we have only started this role last July, we have not accomplished a reduction in unfavourable feedback from the employee survey. But we have achieved a few things:

  1. Through the roadshows, we have met a number of new enthusiastic content owners, willing to help their circle of influence with the new Digital Workplace
  2. Interviews with colleagues who responded in the survey have revealed unexpected and useful feedback.

And that survey…we will do our best to improve the results over time!

An unpleasant inheritance

inherit-picInheriting something is a mixed pleasure.
You can become the proud owner of your uncle’s lovely old-timer, or be able to wear your grandmother’s diamond necklace and matching earrings at grand events, but you generally receive those treasures only after a dear one has passed away.
But you can also inherit debts, a house with an expensive mortgage, a nephew or other “things” that you have never wanted.

Inheriting permissions in SharePoint can also be a curse rather than a blessing.
“I have suddenly lost access” has been the title of many recent incidents. No need to blame this on Microsoft, SharePoint or the support team, because in 99% of cases this is a human error:

  • The Site Owner accidentally removed their own permissions while cleaning up a document library’s  or site’s permissions. The support team can easily fix this.
  • The Site Owner accidentally inherits the permissions from the parent site. That is pretty serious and has happened alarmingly often!
inherit-removeuniquepermissions
A dangerous button that will inherit permissions from the parent – this can be wanted in documents, folders and libraries but can wreak havoc in sites.

I have already mentioned in many of our instruction materials: “if you see “this web site has unique permissions” in the yellow bar, DO NOT CLICK “Delete unique permissions” as you will

  • Inherit the permissions from the parent site
  • Lock yourself out of your site if you have insufficient permissions on the parent site
  • Remove all unique permissions in your site (and there is no “undo” or “restore” option)
inherit-thiswebsitehasnqiuepermissions
If you see this text, you are at the site level!

The warning message appears not to be informative enough to keep people from proceeding.

inherit-warning
The warning message before you inherit the permissions from the parent site.

Recently I have guided a few people through “permissions stuff” via screenshare and I notice that they always want to click ‘Delete unique permissions” when they want to remove users. In several cases these users were individuals who were not in a group and therefore were seen as having unique permissions.
On those occasions I have been just in time to guide their mouse pointers to the right button: “Remove User Permissions”.

inherit-removeuserpermissions
Use this when you want to remove  groups or individuals from your site

This has now happened so often, with such serious consequences, that I have added a suggestion to Microsoft SharePoint Uservoice to rename “Delete Unique Permissions” into “Inherit permissions from parent” as this is probably easier to understand for the user than the current wording. If you agree, please support my request. (Happy to return the favour, of course)

You know, like in SharePoint 2007:

Inheritpermissions2007
What it looks like in SharePoint 2007 – much more intuitive! (Pic taken with Phone)

And if you have taken any measures that successfully prevent this accidental inheritance, please share!

Image courtesy of Phil_Bird at FreeDigitalPhotos.net

SharePoint Holmes and the Missing Menu-item

SPHolmes-EditPageThe case

“I am officially the owner of the site, but I can not manage the site”, the user had written in the description field of the incident.
I asked her what exactly she was trying to do that was impossible, and she said she had wanted to make changes to the homepage of the site.

“But the menu in the gear wheel does not look like the training materials”, she said. “Please see attached screenshot”.

Now that was an interesting screenshot!

SPHolmes-EditPage-Gear wheel
“Site settings” but no “Edit page” in the menu!

I could have asked her if she was able to go to the homepage from the Site Pages or Pages library and if she would have been able to conjure up the Page tab and do it from there, but I was so intrigued by the screenshot that I decided to do some investigation. After all, the “Edit page” option needs to be there and I could better fix that once and for all than waste her time with workarounds. Her problem was not so urgent that she needed the workaround.

And to be frank, I hoped it would turn out to be another SharePoint Holmes topic 🙂

The investigation

  1. Of course, I checked the permissions first. They looked OK. (You know the Dutch words by now, right? 🙂 )

    SPHolmes-EditPage-Permissions
    Owners with Full Control, Members with Edit, Visitors and another group with Read permissions – looks normal!
  2. Yes, she was in the Owners group with Full Control.

    SPHolmes-EditPage-InOwnersGroup
    Mystery Guest is in the Owners group.
  3. I checked the items with unique permissions. The Site Pages library was one of them.
  4. Aha, the Site Pages library had very limited permissions – only Visitors had Read access and that was it. As the Visitors group contained a company-wide AD group, I knew she had access – but only with Read permissions.

    SPHolmes-EditPage-SitePagesPermissions
    Fortunately a wide audience could see the site’s pages – but nobody could edit them!
  5. I checked the Homepage permissions to be on the safe side, and that inherited permissions from the library. So she could see the homepage but not edit it.

The solution

I added the Owners group back to the Site Pages library with the proper permissions. I informed the Site Owner that she had removed the permissions of everyone except the Visitors.
She informed me that “Edit Page” was now in her Gear Wheel menu and she could edit the page again. Problem solved!
I suggested to think about what she wanted to do with this library – keep it like it was with only Owner and Visitor groups (to avoid unwanted edits) or to inherit the permissions from the site.

I wish I had something more deep and interesting to conclude than: “SharePoint permissions are difficult to understand and manage”. 😦

But if you ever come across a screenshot like that, you know what to do!

About SharePoint Holmes:
Part of my role is solving user issues. Sometimes they are so common that I have a standard response, but sometimes I need to do some sleuthing to understand and solve it.
As many of my readers are in a similar position, I thought I’d introduce SharePoint Holmes, SharePoint investigator, who will go through a few cases while working out loud.

Image courtesy of  Clker-Free-Vector-Images on Pixabay.

Beware the SharePoint MVP!

 

No, I am not going to bash the SharePoint Most Valuable Professionals! I have received help, feedback and support from many MVP’s including Veronique Palmer, Jasper Oosterveld and Gregory Zelfond, and I have read and used the posts and presentations of many others.

But I am glad this title caught your attention 🙂

The Minimum Viable Product

This blog will be about another MVP – the Minimum Viable Product, a common word in Agile development, meaning you will launch a product that meets the basic requirements (as defined at the start of the project) and will be improved incrementally over time.

I think I have been woking somewhat agile  when I was configuring solutions, and met with my business counterparts on a very regular basis to discuss the proof of concept/prototype and checked if this met their expectations.
I only created a very small list of requirements, as I knew that many business partners only had a vague idea of what they were really looking for, and when confronted with my interpretation of their requirements all kinds of unexpected, or in any case, unspoken, things came up.

  • Is there an option to leave this field blank?
    Yes, but that means that we either leave this non-mandatory (which may lead to more blanks than you want) or we add a dummy value such as “please select”. What do you think is best?
  • Can we have a multiple choice for this field?
    Ofcourse, but that means you will be unable to group on this in the views, so we will have to resort to a connection for filtering. Oh and then it is better to make this field a look-up field instead of a choice field. Let me rework that.
  • What if someone forgets to act on the email?
    We may want to create a view that allows the business process owner to see quickly which items are awaiting action.

And more of those things. I generally met with my business partner once every fortnight, if not more often.

So I am all in favour of especially the short development cycles of Agile.

“Users” does not mean “end users”, exclusively!

I also think that “user stories” are much more realistic and human than “requirements”, although they sometimes look a little artificial.
By the way, I would recommend any team to think not only of “end user stories” but also of “tenant owner” stories or “support user stories” as other people involved have their own needs or requirements.

Rapid improvements

I also like the idea of launching a Minimum Viable Product and doing small, rapid improvements on that, based on feedback and experiences, because

  • You can show users that you are listening to them
  • You can show that you are not neglecting your intranet after launch
  • It gives you something new to communicate on a regular basis
MVP-DevelopmenttoLaunch
During development, you work towards the Minimum Viable Product

So, when we were launching our intranet I was quite interested to be part of the project and to work towards an MVP.

When we finally launched our MVP we also published the roadmap with intended improvements, and shared the process of adding items to the roadmap.  That way users could see that we had plans to improve and that we would be able to spend time and attention on meeting the needs of the business.

Vulnerabilities

When launching an MVP with a promise to make ongoing improvements you are more vulnerable than when you do a Big Bang Launch & Leave introduction. What about the following events?

  • Cuts in the improvement budget.
    Those can be a blessing or a curse, but they may happen.
  • People who leave before they have documented what they have created.
    I have never liked the extensive Requirements Documents and Product Descriptions that go with traditional development, but if you are handing over your product to the Support organization, you really need documentation of what you are handing over. End users can have the weirdest questions and issues! 🙂
  • Reorganizations which turn your product team or even your company upside down.
  • Microsoft changes that mess up your customizations. We have a webpart that shows your Followed Sites – it suddenly and without warning changed from displaying the first 5 sites you had followed to the last 5 sites. Most annoying!

So before you know it, you end up with a below-minimum viable product. ☚

MVP-Developmentfromlaunch
While in a normal development cycle you would slowly and steadily improve upon the MVP, unexpected events can leave you with something less than MVP.

What can be done?

So before you start singing the praises of Agile development and put on your rose-tinted glasses

  1. Make sure you have a safe development budget that can not be taken away from you.
  2. Ensure you have an alternative no-cost optimization plan, such as webinars, Q&A sessions, surveys, configuration support, content changes etc. to make the most of the launch of your MVP and to get feedback for improvements for when better times arrive.
  3. Insist that everyone documents their configurations, codes, processes, work instructions etc. as quickly as possible. It is not sexy but will save you a lot of hassle in case your team changes.
    If you are in need of extracting knowledge from leaving experts, here are some tips for handing over to a successor, and some tips for when there is no successor in place yet.
  4. Be prepared for changes in processes, data or organization. You do not have to have a ready-made plan, but it is wise to think about possible implications for your product or process if the Comms team is being reorganized, someone wants to rename all business units, or you need to accomodate an acquired company in your setup.
  5. Keep customizations to a minimum. Use existing templates and simple configurations.
    Personally I would be totally content without a customized homepage. The SharePoint landing page or, even better, the Office365 landing page as the start page to my day would work perfectly well for me, but I have learned not many people share that feeling.

Any experiences to share?

Have you had similar experiences? Have you found a good way to handle budget cuts, a way to develop budget-neutrally, how to deal with people changes or another way to deal with unexpected events that endanger your MVP? I am sure there are many people (including myself) who would like to learn from your stories!

Images are from Simon Koay’s totally gorgeous Superbet. Look at that B!
M=Mystique, V=Venom, P=Poison Ivy