3. Why does this topic matter? We find the issues in SharePoint typically when SharePoint upgrades, new third party components, new solutions and significant changes are made to SharePoint. This results in high costs and greater delays than if many of those issues had been discovered earlier.
4. What we will be talking about… What is a SharePoint Prescription? SharePoint Preventative Care SharePoint Palliative Care SharePoint CurativeCare SharePoint Incident Reporting SharePoint Health Assessments
18. What is Preventative Care? Measures taken to prevent diseases (or injuries) rather than curing them or treating their symptoms. In SharePoint Terms? The pro-active actions you plan for, schedule and execute to mitigate or prevent issues from occurring in your SharePoint implementation.
19.
20. What are people searching for and what are they not able to find?
24. Look at the reports available in SharePoint Designer.
25.
26. If you are upgrading to SharePoint 2010 this is also important to understand as the default throttling limits may impact user experience.
27. SQL Scripts (Read Only) and API calls can help identify what lists you do have over the default throttle settings, and which have a larger lookup count.
28.
29.
30. Do you know how complex the SharePoint Designer workflows are in your environment?
47. Database Growth Example A site collections content database is 60GB in total size. Preventative Action: Set alert to warn if the content database goes beyond 80GB in size and schedule reports on storage space and database growth.
48. The Outcome You are able to prevent many potential SharePoint issues through careful planning.
49. What to watch out for… No one wants to do preventative care or pay for it. “It won’t happen to me.”
51. What is Palliative Care? Any form of medical care or treatment that concentrates on reducing the severity of disease symptoms, rather than striving to halt, delay, or reverse progression of the disease itself. In SharePoint Terms? Targeting and fixing symptom like issues within your SharePoint implementation without targeting or solving the root cause.
52.
53. You are under artificial constraints that make the potential solutions for the underlying issue infeasible until a later time.
56. SharePoint Example A site collections content database is 60GB in total size. Preventative Action: Set alert to warn if the content database goes beyond 80GB in size and schedule reports on storage space and database growth. The content database grows quickly to 100GB in total size. The warnings have been sent out. Palliative care would be to either split the content database up or to adjust processes so that the content DB can continue to grow beyond 100GB.
57. The Outcome Symptoms of an underlying SharePoint issue are resolved to decrease the impact of the underlying SharePoint issue.
58. What to watch out for… When a symptom is treated it doesn’t cure the underlying issue.
60. What is CurativeCare? Actions that seek to cure the existing disease or medical condition. In SharePoint Terms? Solve the underlying issue/problem so that it no longer exists in your implementation.
65. Effort needs to be taken to determine an automated synchronization solution for the HR Employee Directory and Active Directory data or one of the systems for managing employee information should be retired so that it can be contained and managed from one source identity/profile. This is because some people are updating user profiles in SharePoint. Some are contacting help desk or HR to get their information updated when addresses or phone numbers change. There are several known challenges. When a user updates their information in SharePoint it does not update Active Directory resulting in updates to the contact information in Exchange. When Help Desk updates user information they do it in Active Directory. When HR updates user information they do it in the HR Employee Directory (Custom/Not Active Directory).
66. Do I Need To? Before you go through a medical procedure the doctor would explain the procedure and the risks, options and alternativesallowing the patient to make an informed decision about whether the risk was worth it. We must do the same with SharePoint solutions – the risk is theirs to take, not ours. Not if there are no known or identified issues.
67.
68.
69. What to watch out for… We cannot cure something if we don’t know enough about it.
71. When to Assess When not scheduled it’s still important to perform assessments after any “curative” action is performed. “It indicates that the prescriber takes responsibility for the clinical care of the system and in particular for monitoring efficacy and safety.” Additionally it may be best to perform one after significant palliative or preventative measures are taken.
72. Incident Reports An incident report or accident report is a form that is filled out in order to record details of an unusual event that occurs at the facility, such as an injury to a patient. The purpose of the incident report is to document the exact details of the occurrence while they are fresh in the minds of those who witnessed the event. Some iatrogenic artifacts are clearly defined and easily recognized, such as a complication following a surgical procedure. Some less obvious ones can require significant investigation to identify, such as complex drug interactions. In SharePoint Terms? If something unusual happens as a result of ‘preventative’, ‘curative’, or ‘palliative’ measures being taken it must be documented with as much detail as possible while it’s still fresh in the minds of those who were participants or effected.
74. Mental or Physical? Physical health without mental health is not ‘healthy’. In a SharePoint Implementation: Physical Health = Technical Health Mental Health = Business or Non-Technical Health If you have business or non-technical issues you do not have a healthy SharePoint implementation.
211. Do you have clearly defined SLAs for support and problem resolution?
212. Do you offer face to face learning or unstructured/semi-structured environments for learning? (Lunch and learns, after hours discussions, communities etc)Support Assessments
297. The Diagnosis Diagnosis is used to help determine the causes of symptoms, mitigations for problems, and solutions to issues.
298. What to watch out for… “Prescription without Diagnosis is Malpractice.” “Prescription of a SharePoint Tool/Solution/Implementation without Diagnosis is Malpractice.” Please Share This!
299. What we talked about… The Plan of Care for SharePoint PreventativeCare is critical and cost effective. Palliative Care targets side effects and is expensive. Curative Care is difficult without clear diagnosis. Record and Learn from Results Assess Often, Target Assessments, Act on Results What is a SharePoint Prescription? SharePoint Preventative Care SharePoint Palliative Care SharePoint Curative Care SharePoint Incident Reporting SharePoint Health Assessments
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?
The audience for these assessments shouldn’t always be a technical one. Often we get lost in delivering assessments to the caretakers without delivering to the real patient which is the business and business users themselves. In our example above we described Technology Experts as the caretakers of the organizations technology needs and health. Realistically though for assessments that deal with user adoption, governance, or organizational maturity we are dealing with something beyond the technology. We want to encourage behavior changes (for the better). What better way to do that than by also delivering to the business and business users as well as the caretakers?