Moving content services to the cloud: Step 1 — Assessing
Content, and the processes surrounding its creation, management and execution, are broad concepts. A good place to start in assessing your needs is to identify the content you have. Every organization has “unknown unknowns” within their content and related practices. Perhaps there’s a trove of HR content that lives on an old server, or maybe cross-departmental teams struggle to collaborate and serve customers because no one can agree on which format to use.
Neither of these scenarios are ideal, but they are perfect examples of the type of unknown you are trying to uncover as you audit your content.
The information gathering and assessment stage of your capabilities will help you triage the problems that need to be solved and shape the questions you ask potential partners. Think of this exercise as bringing a fresh set of eyes to each piece of content and the practices surrounding it.
|
What it is |
Where it’s found |
Who owns it |
Customer content |
Applications, forms, supporting documentation, constituent correspondence and emails |
CRM and ERP platforms, homegrown or outdated case management systems, shared drives |
CIOs and IT leads, customer service teams |
Procedure content |
Manuals, workflow documentation, privacy, training and certifications, document retention |
Physical locations, shared drives, intranets |
COOs, department leads, records managers, project managers |
Back-office content |
Accounts payable and receivable forms, financials, contracts, grants, GIS |
Secure servers, payroll systems, accounting dashboards, ESRI |
CFOs, AR and AP team leads, accountants, planners |
HR content |
Personnel files, onboarding and offboarding information, disciplinary actions, benefits guides |
Intranets, shared drives, employee handbooks |
Intranets, shared drives, employee handbooks |
Miscellaneous and internal content |
Historical documents, reports, archived emails, spreadsheets, research |
Individual drives, old servers, unorganized departmental files |
Can be owned by anyone |
As you audit this content, be mindful of opportunities to improve and problems to solve. Most likely, the challenges you uncover will align with one of several overarching goals:
- Improving security/disaster recovery
- Improving accessibility
- Finding cost savings
- Supporting a remote workforce
- Streamlining processes
- Increasing data availability/uptime
- Incident response
- Handling geographical disbursement of content
Gathering stakeholders
Once you have identified and ranked the projects you’ve chosen to pursue, engaging all the appropriate internal stakeholders is an important next step. During this process, you want to identify every employee that will touch the rest of the process, from vetting potential solutions to measuring the end result of the deployment. This will help you align on strategy and avoid situations where leadership is misaligned with the needs of different departments or functions.
Setting the scale and starting the search
Once you know the issues you’re working to solve and you have your team gathered and aligned, the next consideration is one of scale. The best content service platforms and applications can handle a range of problems from large to small — it will be up to you to determine how aggressive a strategy to choose. Some considerations when determining scale:
Timing
How quickly do you want to launch, and how fast do you expect to see results? This critical determination will inform the budget and the priority of the project.
Budget
The amount you have to spend will play a major role in determining how large the engagement can be. Thankfully, the modular nature of many platforms helps with this.
IT capabilities
Keep initial projects small, and scale them according to your IT team’s skill.
Strategic alignment
Certain projects may make more sense because they align with a similar goal or technology deployment occurring in another internal department. If one department is pursuing a solution that also helps you, is it possible to align?
Priority
No project needs to be a “lift and shift” of everything to the cloud. Instead, you may have one or two critical needs that can be addressed with a proof of concept or smaller departmental deployment. These projects can help you make big impacts in relatively short time spans — with less disruption.