Trying to decide what to post about after a long hiatus…
SharePoint is a great tool supporting collaboration!!
What exactly IS collaboration?
Go ahead- define it. I’ll wait.
Does your response looks something like this?
“Activity leading to increased efficiency”
Or “People working together to achieve a common goal”
Or maybe even, “Improving team outcomes by participating in common tasks according to best practices.”
All good tries. But esteemed SharePoint expert Paul Culmsee (@PaulCulmsee) calls those types of phrases “platitudes.” He defines them as “Words or phrases that sound impressive and correct but ultimately do not contain a lot of substance… also defined as ‘a trite or meaningless statement made to sound profound.”
Hmm. This sounds like platitude-users are knowingly trying to put one over on their listeners. This is not usually the case. Most of the time, these types of statements are made with complete sincerity, and are perceived by those making them as being the right response to a given question or situation.
But there is a problem with platitudes as goals, mission statements, vision statements, purpose statements etc., especially in the case of SharePoint. To spend a lot of money on technology and the people using it requires (usually) that the “bang for the buck” can be at least articulated, if not captured and measured and shown to prove success. Platitude statements are too vague to suffice in those circumstances.
If your definition/purpose statement for SharePoint is anything like this: “A tool to support increased collaboration and efficiency,” there may be cause for concern. How will you know if you have accomplished either of those things?
How will you measure the results? How will you recognize a state of affairs that is any different from how it was before SharePoint came into your life?
Some other common platitudes:
- Quality (i.e., ‘increased quality,’ ‘improved quality,’ ‘better-quality widgets’)
- Governance (see also, ‘a governance plan’)
- Streamline business processes
- Improve communication
So how do you get past the fuzzy phrases? (Culmsee calls this “busting a platitude“). You have to continually ask questions like, “What does [platitude] looks like?” or, “Can you describe how [platitude] would be recognizable in your company or in the course of your daily work?” or “What are some of the behaviors displayed by people in a workplace that have [platitude]?”
Paul’s presentation goes on to explain the benefits of asking questions like this. If you’re lucky, the answers tend to start with things like, “increased this…” or “decreased that…” If so- that’s good because these responses indicate items are often inherently measurable. This means you are on the right track.
BUT- sometimes you get answers that are just another platitude! Such as, “Increased efficiency would result in better-quality widgets.”
So you must ask again. “If you had increased efficiency, what would that look like? How would we recognize that efficiency had increased? And then, how would we know that widget quality was any better than it was before?”
Anyone considering use of a product like SharePoint must be able to articulate- WITHOUT resorting to platitudes– what SharePoint is supposed to be doing in whatever context it is being used. What is your “SharePoint purpose statement?”
All responses welcome! Leave a comment and share yours.
If you have not taken the time to read Paul’s articles, you are missing out! DO it now.
I’ve had to have several conversations about SharePoint alerts recently. These conversations have revealed to me that many site owners don’t grasp that alerts are designed to be an “end-user empowerment tool” to facilitate self-service notification about SharePoint site activity. Alerts are not really intended to be an administrative tool for owners to “force” notifications onto site users or control how they work. Why is this so hard to understand?
This misperception can cause problems if that concept is not fully embraced. SharePoint assumes and expects that users are able and capable of managing how they want to be notified, and will appreciate/use the tools allowing them to do so. Savvy site owners will realize there is little value in choosing not to leverage this behavior. Why take on that responsibility? Choose to use alerts as they are intended. Instead of laboring over administration and control of alerts, use that time and effort to educate users about alerts and how they can be one of the most powerful aspects of SharePoint.
OOTB, site owners (or anyone with the Manage Alerts permission) can create and delete alerts on behalf of other users, but beyond that, alerts-for-others become the “responsibility” of the users for whom they were created. Included in that scope is the fact that at any time, any user is free to delete or change any alert put in place on his/her behalf, with zero awareness shared with the alert creator. Set up all the alerts you want, site owners; but just know that your users can delete them as fast as you can set them up.
For example: Joe Owner creates an Announcements List alert that sends an immediate email to 5 users and himself when new items are added. After a couple of days, Joe decides that this is too many emails, and wants to change the alert from an immediate email to a daily digest. He finds that he can only modify HIS own relationship to the alert parameters. It is not possible to change/remove a “mass” alert in one action. When he updates his own instance of the alert, his changes are not “rolled out” to the other 5 users. They will continue to get the alert according to the original set-up. To stop the original alert, Joe would have to remove it manually for each individual (or ask them to it themselves), then recreate the alert with the new daily digest settings for those 5 users. See the potential administrative burden? Who wants that?
A frequent question is: How do I see alerts on my site?
Basically, this depends on your role:
Site Owners: To see the listing of all users who have alerts associated with them on a particular site:
Go to Site Settings > Site Administration > User Alerts (see image).
A drop-down box will say “Display alerts for.”
Select a user and then click “Update.”
You will see a list of all alerts in place for that user.
Mark the check box to select an alert and click “Delete selected alerts” to remove them.
NOTE: It only works in this direction- there is no option to see all alerts and then the associated user name(s).
On the next page, locate and click the “My Alerts” link (top center, sort of small, above your user information).
The next page displays all alerts associated with the user (self-created OR created by others).
The user can then modify or delete any alert.
Companies that want to expand the alert scope into a more admin-focused tool usually end up purchasing a 3rd party add-on, such as the one linked from this article. Also, developers can modify the alert framework by reprogamming default options. See this posting for some of those possibilities.
Excellent overview of SP 2010 workflow creation.
Workflows are a real poweful tool built-in in Sharepoint since 2007 version as you can design it to add logic to your site or application without any custom coding! This can be anything from automating business processes, sending notifications or even as simple as creating tasks. There are a lot of possibilites which is only limited by your imagination.
View original post 739 more words
The prospect of something getting deleted from SharePoint can strike fear into the hearts of many users. So much fear, in fact, that they go to extraordinary lengths to try to make it so that no one CAN delete anything…. EVER. But think about it- SharePoint is not a catch-all or a bottomless archive. SharePoint is generally meant to hold active content that matters- in real time- to you and your colleagues. Sometimes people need to delete things. Sometimes people SHOULD delete things.
Don’t you know that SharePoint has your back? Use the tools at your disposal to ensure that you’ll never be the last to know when someone deletes a document or a list item, and give you ample chance to restore it if necessary.
What is SharePoint?
“SharePoint is increasingly an eclectic kit-bag of publication and collaborative tools, services and features that can be used somewhat like a Lego set to build technology solutions driven by business need. Receiving SharePoint for the uninitiated is rather like being given a toolkit as a gift. The first question would be: what do I do with this? Build something is the answer. Build what? Whatever you want or need to build. I’m not sure what I want, is there a blueprint or plan? No. Can we build what someone else has built? Sure. Can you help us build something the same as someone else has? Sure yes. How much will it cost? It depends what you want, we will need to discover what your specific needs are. Yes but how much will it cost as a ball-park figure? It depends on what you want. I want what everyone else has! Ah but everyone else is different so we cannot tell you how much it will cost and how long it will take until we have defined your exact requirements. And so it continues…
“In other words, the SharePoint toolkit is powerful but without a logical, progressive business plan, blueprint or roadmap alongside SharePoint is extremely difficult for a business audience to imagine in terms of a future, valuable whole. Business stakeholders have a requirement to describe SharePoint to their own internal audiences and this is frequently where initial problems occur. They call in a Partner to demonstrate the value of SharePoint in an hour. What is all too often described is a technical demonstration of a team site, or a workflow, or a form, or version control etc. SharePoint is being described both by some isolated features, and in isolation of a fuller business context.
“This issue regarding describing SharePoint is often anticipated by Partner Sales Managers prior to a client presentation by requesting some specific problems the business may be prioritizing and basing a pitch and demonstration regarding how SharePoint can solve these specific problems. Therefore SharePoint, as an enterprise platform, is all too often described in these situations primarily as a project-specific technological solution. What happens when that problem is solved – where does the client go then, what does the business do next, what else can they build? And so we come back to the same dialogue as before. What other problems do you have? What other priorities can we assist you with? How much budget do you have? It is because of this scenario, played out hundreds of thousands of times globally that a number of things have occurred that have assisted in defining SharePoint in a specific way. The first is the flexibility of solution design and delivery. This has led to SharePoint rather frequently being described as a ‘development platform’. ‘Tell us what you want and we will build it’. Ah, says the client, but we don’t know what we want. ‘It’s okay’ says the platform developer, SharePoint can be used to develop and provide you with anything and everything you want. Within a short space of time of the introduction of SharePoint solutions are being built without any form of business plan.”