Win-an-eBook Wednesdays is a small three day contest that we hold every week. The Prize? An O’reilly eBook for your choice! Furthermore, if you win, you also get the chance to ask the community whatever question you want and be the judge for next week’s contest!
The only thing you have to do to enter is answer the following question: How do you say NO in a SharePoint world?
This week’s judge is Stephen Tierney , winner of last week’s contest( He got the Microsoft SharePoint 2013 Developer Reference eBook).
Stephen’s Comments:
Sometimes as a Developer, Admin, Manager or End User we have to say No. SharePoint is a platform so it can do anything right? Sometimes the requests are a little out there and you have to say No to a feature, tool or even push back as an end user. How do you do that without being the bad one?
You have until Friday 26th (10pm GMT) to answer this question!
And the winner is….
BattleSmith!
I’ve really enjoyed reading everyone’s answers and they have all been great answers at that. In the end though there can be only one (yes I went there)………. answer and that was BattleSmith. When I asked this question I was looking to see who could give a real world example in SharePoint when they have pushed back and BattleSmith provided that with something I have also came across in my time with SharePoint.
Well done sir 🙂
“We will be happy to assist you. Please send us a written request and we will prioritize accordingly.”
I have outsourced the no-saying to my calendar, I simply do not have enough time…
Quite convenient in a way actually .
Saying NO usually leads to this conversation:
What do you want? – No, we can’t do that
So why would you want that? – Hmmm, in that case you might actually want something else
Back to the beginning, what’s your actual problem? – Ah, I see some possiblities there
But tell me, do you REALLY need that bit? – See, then it becomes less of a problem
So tell me again: what do you want? – Sure, will do!
But really (to disqualify my own answer…) that has more to do with software development than it has with SharePoint.
