Service Architecture and Setting Up ServiceNow

Below is a simple step by step guide to setting up a personal developer instance of ServiceNow

  1. Sign up for ServiceNow: Visit the ServiceNow website and sign up for a developer account if you don’t have one already. You might need to provide some basic information.
  2. Access your Developer Instance: Once you’ve signed up, you’ll be provided with access to a ServiceNow Developer Instance. Log in to your instance using the credentials provided.
  3. Explore the Instance: Take some time to explore the platform and its capabilities. ServiceNow offers a wide range of services including IT Service Management, IT Operations Management, Security Operations, and more.
  4. Customize Instance Settings: Depending on your requirements, customize the instance settings such as language, time zone, and currency.
  5. Create Users and Groups: Set up users and groups according to your organizational structure. Assign roles and permissions to control access to different parts of the platform.
  6. Define Service Catalog Items: If you’re using ServiceNow for IT Service Management, define service catalog items such as incident reporting, request forms, and service requests.
  7. Configure Workflows: Design and configure workflows to automate processes within your organization. ServiceNow’s Workflow Editor allows you to create complex workflows with drag-and-drop functionality.
  8. Integrate with Other Systems: ServiceNow supports integration with third-party applications and systems. Configure integrations to streamline processes and improve efficiency.
  9. Test and Deploy: Before deploying your instance for production use, thoroughly test all configurations and workflows to ensure everything is working as expected.
  10. Training and Documentation: Make sure to train your team on how to use ServiceNow effectively. ServiceNow provides extensive documentation and training resources to help users get started.
  11. Monitor and Maintain: Once your instance is up and running, regularly monitor its performance and usage. Perform regular maintenance tasks such as applying updates and patches to keep the system secure and up-to-date.

Following these steps should help you set up a basic instance of ServiceNow and start leveraging its capabilities for your organization’s needs.

Service Architecture and the Service Design Lifecycle

Introduction

The Service Design Lifecycle is a structured approach to designing and implementing IT services within an organization. It encompasses a series of phases, each focusing on different aspects of service design, from initial concept development to final implementation and ongoing improvement. By following the Service Design Lifecycle, organizations can ensure that their services are aligned with business goals, meet customer requirements, and deliver value effectively.

Phases of the Service Design Lifecycle

The Service Design Lifecycle consists of the following phases:

  1. Strategy:
       – Definition: In this phase, organizations define their strategic objectives and align them with the overall business goals. This involves understanding customer needs, market trends, and competitive dynamics.
       – Service Portfolio Management: Organizations develop a comprehensive portfolio of services that align with their strategic objectives. This includes identifying existing services, defining new service offerings, and retiring outdated services.
  2. Design:
       – Service Catalog Management: Organizations create a catalog of services that are available to customers. This involves defining service definitions, descriptions, and pricing information.
       – Service Level Management: Organizations define service level agreements (SLAs) that specify the level of service quality, availability, and performance expected by customers.
       – Capacity Management: Organizations ensure that they have the right resources in place to deliver services effectively. This includes managing infrastructure capacity, performance, and scalability.
       – Availability Management: Organizations ensure that services are available when needed by customers, minimizing downtime and disruptions.
       – IT Service Continuity Management: Organizations develop plans and procedures to ensure that IT services can be recovered quickly in the event of a disaster or disruption.
  3. Transition:
       – Change Management: Organizations implement changes to services in a controlled and systematic manner, minimizing risks and disruptions.
       – Service Asset and Configuration Management: Organizations maintain accurate records of service assets and configurations to support effective change management and decision-making.
       – Release and Deployment Management: Organizations plan and manage the release and deployment of new services or updates to existing services.
  4. Operation:
       – Incident Management: Organizations respond to and resolve incidents that impact service availability or performance, restoring normal operations as quickly as possible.
       – Problem Management: Organizations identify and address the root causes of recurring incidents to prevent future disruptions.
       – Event Management: Organizations monitor events and alerts to detect and respond to potential issues before they impact service delivery.
       – Request Fulfillment: Organizations fulfill service requests from customers in a timely and efficient manner, ensuring customer satisfaction.
  5. Continuous Improvement:
       – Service Measurement and Reporting: Organizations measure and report on key performance indicators (KPIs) to evaluate the effectiveness of services and identify areas for improvement.
       – Service Review Meetings: Organizations conduct regular review meetings to assess service performance, identify opportunities for improvement, and make adjustments as needed.
       – Service Improvement Plans: Organizations develop and implement plans to address identified gaps or deficiencies in service delivery, driving continuous improvement over time.

Conclusion

The Service Design Lifecycle provides a systematic and structured approach to designing, implementing, and managing IT services within an organization. By following the phases outlined in the Service Design Lifecycle, organizations can ensure that their services are aligned with business objectives, meet customer requirements, and deliver value effectively. Investing in service design and management processes is essential for organizations seeking to optimize service delivery, enhance customer satisfaction, and drive business success.

Service Architecture and the Service Design Pack

Introduction:
Service Design Packs are the staple part of the work completed by a Service Architect in response to a set of Requirements. The documents represents the processes, tools and people required to manage a Service to the documented requirements and to the agreed quality criteria i.e. Service Level Targets (SLT’s), Key Performance Indicators (KPI’s), Key Results Areas (KRA’s). The document is key to getting the agreement from key stakeholders on all of the design areas and forms the basis of the activities that will be included in the Service Transition Plan.

Key Components:

  1. User Personas: These are fictional characters that represent different customer demographics and help the Service Architect understand key and distinct needs for different groups of users.
  2. Customer Journey Maps: Mapping out the customer journey allows providers to visualise the various interactions points and the understand various pain points and opportunities for improvement.
  3. Service Blueprints: Service blueprints provide details of how the service is delivered and which can include both front stage and back stage of the services operations i.e. those that the customer can see and those they can’t. The Blueprint is used to outline the sequence of actions undertaken between customers, staff, and supporting systems that ensuring the consistency and efficiency in service delivery.
  4. Prototyping and Testing: The Service Design Packs should include those activities required to prototype a new service along with any service interfaces, processes, and systems. This allows for iterative testing and refinement and ensure that the final service meets customer expectations in accordance with the requirements
  5. Service Standards and Guidelines: The SDP should establish any new changes of deviations to any of the organisations policies, processes and procedures. The changes may need to be reflected in the organisations standard documents or stated within the SDP that they are tactical short term measures
  6. Training and Development: Service Design Packs should include requirements for Knowledge Development and which can drive the production of or change to training materials and resources for staff.
  7. Measurement and Evaluation: Key metrics such as SLT’s and KPI’s are essential and allow service providers to assess the effectiveness of their services. By tracking metrics such as Customer Satisfaction, service demand and usage, organisations can drive further improvement and enhancements to the service.

Benefits:

  1. Enhanced Customer Satisfaction: By focusing on understanding customer needs and preferences, service design packs enable organizations to deliver services that resonate with their target audience, leading to higher levels of customer satisfaction and loyalty.
  2. Improved Operational Efficiency: Clear service blueprints and standards streamline operations, reducing inefficiencies and redundancies in service delivery processes. This results in cost savings and better resource utilization for service providers.
  3. Innovation and Differentiation: Service design packs encourage creativity and innovation in service delivery, allowing organizations to differentiate themselves from competitors and offer unique value propositions to their customers.
  4. Agility and Adaptability: The iterative nature of service design allows organizations to adapt quickly to changing customer demands and market trends. Service providers can continuously refine and optimize their services based on real-time feedback, ensuring relevance and competitiveness in the dynamic business landscape.

Conclusion:
Service design packs are invaluable tools for organizations seeking to design and deliver exceptional service experiences. By incorporating user-centric principles, best practices, and continuous improvement methodologies, service design packs empower organizations to create meaningful connections with their customers and drive long-term success in today’s service-driven economy.

Service Architecture and Use Cases

What are Use Cases? Use cases are used to describe, capture, model, and specify the requirements of a service or system.  

Use Cases are invaluable because they help place the Service Architect in the footsteps of the user of and actors who provide the Service. Use Cases provide a foundation to guide questions about what needs to happen to satisfy the end user and allows the capture of what’s important. With a solid Use Case, a Service Architect can then build a solution that is prioritised around service to the end user and gives clarity to the actors as to what activities and tools they will need to provide the desired outcome.

Consider an example from the IT world below.

Use Case – New Joiner to the Sales Dept of a company, requires access to various systems and applications to perform her role.

  1. The Line Manager needs to place an order for a new starter and requires access to the companies IT Product Catalogue so that they can select the most appropriate device for the role along with role specific applications
  2. The Line Manager needs to able to perform a search for an appropriate bundle of devices and role specific software for a Sales person
  3. The Sales New Starter Bundle needs to consist of:
    • Hardware
      • Laptop
      • Power Supply
      • Mouse
      • Mouse Mat
      • Headphones
      • Carrier bag
    • Software
      • Microsoft Office including Teams for collaboration and PowerPoint for presentations
    • Other
      • The user will need an Instruction Manual that guides them through the setup process, how to operate and what to do when things go wrong.
      • The Windows 10 build needs to be specific to the Sales Organisation, which comes with Organisation Branding on the front screen and allows access to USB devices and screens for presentation
  4. The Sales New Starter Bundle request needs to be approved by
    • Budget Owner
    • Head of Sales
    • HR
  5. The Sales New Starter also has to provide them access to a Teams Folder and Salesforce with the correct permissions for the various folders
  6. Access to Salesforce and Teams Channel is managed by the assistant to the Head of Sales who require notifications of setup through an email once the device has been shipped
  7. The New Starter Bundle Request is supplied by a Outsource Provider, XXXYYY Ltd who will take a Laptop from storage and build it using the agreed configuration which is owned and developed by the IT Department. The Build is known as Sales Build V0.1
  8. XXXYYY Ltd will Asset Tag the machine and update the Asset Data in the ITSM Tooling ServiceNow
  9. XXXYYY Ltd will hand the device to the Shipping Company AAABBB Ltd who will update the Request in ServiceNow
  10. AAABBB Ltd will scan the Asset Tag into their Shipment Tracking System and proceed to deliver the device
  11. AAABBB Ltd deliver the device to the end user and take a photograph as proof of delivery which is uploaded to the Shipment Tracking System
  12. ServiceNow automatically sends out an email the next day to close the request OR ask the End User to mark the Request as failed with a reason

Service Architecture and Mining for Opportunities

Applying Service Architectural principles offers a gold mine for structuring opportunities. The Customer Experience Map allows a Service Architect to build a picture of what the driving forces and constraints are within the business i.e. what pressures there are. Sometimes there are pressures driving the environment forward and there are often pressures holding an organisation back.

Finding out what’s important to your client offers an opportunity to agree a set of design principles. These principles can then be used to prioritise and select the most appropriate response to the problem to be solved.

As a next step, the Service Architect can baseline the existing service or business by breaking processes down into stages, finding out what the key activities are and then looking for pain / pleasure points i.e. what emotions are people feeling. The Design principles then add some structure to what’s important (a sort of pareto principle can apply here) and in conjunction with feelings states allows the opportunity to craft a response, moving the actors in the process into better feeling states. This is crucial, after all, we are all people

The Role of a Service Architect

Over a 30 year career I have covered many types of roles within IT. I started as a Mainframe Operator, before going onto be a LAN Manager and then a Network Designer at Barclays Bank. I then moved into Technical Management and from there Services Management and Project Management.

Although I have a very clear view of my role as a Service Architect, it is common for me to sway a little outside of that. Having spoken to many of my colleagues, we all have similar experiences of doing things outside of the standard role of Service Architecture. How many capabilities and roles do you fulfil in your role. Here are some of mine:

Business Analyst. I often take ownership of the development of requirements, especially the development of non functional, service requirements. Also develop process maps and processes in order to support the development of requirements

Project Manager. In large programmes where I’m part of a project team there is often a dependency on developing “core services” or “core capabilities” and these need project management. As a Services Lead, I will often create plans that enable delivery in workstreams and projects

Service Architect – need I say more

Test Manager / Test Assurance Manager – If I am developing requirements and designing services, I may sometimes act as a Test Manager to ensure service based testing is complete. For instance, the implementation and testing of Catalogue Request items in ServiceNow.

Knowledge Manager – I see part of my role as ensuring all the Knowledge Articles are correlated, updated, retired and fit an overall approach and strategy

Finance and Budgets Manager – I often play a part in outsourcing projects where I may need to use my experience to financially size or cost model a service

Stakeholder / Business Change Manager – Managing stakeholders is a key part of the work undertaken by a Service Architect. I often see myself as the subject matter expert who provides a conduit into the project world for those who will receive the service in BAU. Also, I will act as a Subject Matter Expert to the programme or project when wanting to know more about BAU operations

Friend / Colleague – I act as a friend to my colleagues in order to support them in the development of their own Service Artefacts. For instance, doing peer reviews

So, how many roles to you play?

Service Architecture and the Service Design Package

So what is a Service Design Package and what’s it purpose?

The Service Design Package is a document that describes the services that are to be delivered and managed within the scope of the project.

The purpose of the document is to describe the services including the processes, people, partners and technology to be offered by the service to the end user and that support is management to a level that can be understood and ultimately approved by all stakeholders.

One of the most important aspects of the SDP is to call out what is being offered to the end user i.e. the products or services the end user receives. A common mistake made by service practitioners is to confuse the service with the product. For example, M365 (Microsoft 365) offers many products such as Word, Excel, One Drive etc but these are often listed as services.

Checklist Service Design Package SDP | IT Process Wiki (it-processmaps.com)

Service Models – A Picture Paints a thousand words

Do you ever see people’s eyes glaze over when you talk about services? Or even worse, you send a 40 page Service Design Package to various stakeholders who don’t read them because they’re just too much and they’re as busy as everyone else?

Part of the job of a Service Architect is to make something fairly nebulous

A traditional Service Design Pack sometimes just isn’t the vehicle to explain how things work. In the modern busy world, I’ve seen a lot more success when effort is spent on creating simple diagrams that give stakeholders a simple understanding of what it is you are trying to convey. When they “get it” you’ll find they’ll get behind you when it comes to overcoming obstacles in the detail

I’ll say no more 🙂