Insights

Stop overloading your Sitecore team, consider hiring a system admin

August 03, 2016

Sitecore started as a Content Management System and over time has added different technologies to its core. These technologies have contributed to Sitecore's current status as a market share leader*. All of these changes have improved your experience and helped you build deeper customer relationships by focusing on their experiences. On the other hand, these changes also increased the complexity of Sitecore's environment.

If you are about to embark on a Sitecore implementation, please be aware that purchasing the license won't deliver the best experience, in fact it is only the first step.

And what are the next steps?

As you probably know, every project has its singularities and Sitecore is no exception to the rule as it relies on specifications to properly answer various questions. However, most projects share a few commonalities:

In addition, given the fact that Sitecore has become a powerful, scalable and flexible platform, you shouldn't overlook the design and scale of your structure otherwise you risk letting the project go down the drain.

How can I avoid that?

Sitecore is on another level when it comes to its capabilities, features, experiences and most notably, its complexity – because of this, we recommend that you strongly consider adding a new member to your Sitecore team.

A new member?

Yes, a system administrator.

Many companies don’t have a dedicated system administrator, and instead have a single employee trying to cover both their own role and the role of system administrator.

The point here isn't to undervalue that person’s abilities or the job they’ve been able to do until now, but to add someone who can bring more expertise and add extra value during future Sitecore projects, and ideally, on an ongoing basis.

My team has never used a system administrator, can't I continue without one?

Some people say, "If it ain't broke, don't fix it".

Well, the Sitecore platform has changed and grown in many ways over the years. So, why shouldn’t your team?

Alright, but can you point to some benefits of this?

System administrators can contribute in many ways before, during, and after on a Sitecore implementation:

  1. Conduct prerequisites analysis before the project starts
  2. Check hardware to ensure it fits the specifics of each project
  3. Define and implement High Availability plan
  4. Define and implement Disaster Recovery plan
  5. Define Sitecore strategy (e.g., in Cloud or in House?)
  6. Install Sitecore (e.g., Scale and Harden)
  7. Install and configure the Sitecore xDB (Experience Database) and Solr
  8. Setup servers (e.g., Windows patching and IIS installation)
  9. Conduct license analysis (e.g., Buy or adjust, Sitecore and MongoDB)
  10. Define security requirements (e.g., Firewall, DMZ)
  11. Conduct protocols analysis (e.g., SMTP, Webservices)
  12. Troubleshoot along the way

Consider adding a system administrator to the project (and, ideally long after is complete!) to contribute and to ensure you aren’t overloading your team with responsibilities. Your team will thank you for it.

Keep the rest of the team focused on the solution in order to succeed with your Sitecore implementation. Now, get to work improving the customer experience!

*market share leader

Meet The Challenges Of Today's Digital Economy

Ready to take that first step and rise to your digital potential? Contact Valtech today.
Talk to Us