In life, just as in business, we need to plan for the unexpected...There is a plan in place and people trained to take over when the need arises
One of the things that separate information managers from IT folks is that IMers can't tell their left from their right. We don't write code. We decode. We don't wire offices. We observe how the folks in those settings are wired. We make a clear distinction between the network...
#SharePoint #requirements #usecases #Collaboration #knowledgemanagement #planning #Collaboration
1 Comment - If you understand your people, processes and technologies you can then put together a plan to support those people, processes and technologies
Instead of receiving "plans of action" I received all kinds of good advice on ways one can go about collecting requirements...That perhaps all I can expect to receive are generalizations and tips, not concrete plans and detailed answers
Think about some popular KM techniques: • On-the-job training • Mentoring • Coaching • Apprenticeship • Succession planning • Networking • Teaching • Publishing These all have a common purpose – knowledge transfer, and they all require active participation
With proper planning and some crafty use of open source technology... absolutely
And do you know any cutovers, backways or shortcuts from talking points to a proposable action plan?
The roadmap will provide the game plan to get you from the current state to future state...Investing in this type of planning will help maximize the ROI of SharePoint and set the foundation for a successful deployment
Leary): L earn -- Includes templates, frameworks, videos, publications, onboarding materials S ell -- Includes proposals, qualifications, and discussions that grease your pipeline D o -- Includes the diagnostics, planning, and delivery of your work product So there you have it
In a business context, what about the collective choices made by an IT department moving forward on a plan based on faulty data?