Latest Articles

Stop Building Workflows from Scratch — Use Task Lists and Action Flows for Employee Services The Pattern Problem Most employee service requests follow predictable patterns. New hire onboarding, hardware asset assignment, access provisioning—these are repeatable processes that can be standardized. Yet many organizations still handle each request from scratch, leading to inconsistency, delays, and unnecessary manual effort. The Solution: Predefined Workflow Components Modern service management platforms provide tools to streamline employee service requests through three key components: 1. Task Lists Task lists define the predictable, repeatable steps required for common service requests . Examples: New hire onboarding: Equipment setup, account creation, access provisioning, training scheduling Hardware assignment: Asset selection, configuration, shipping, user setup Access requests: Approval gathering, provisioning, confirmation Benefits: No one forgets a step Consistent process every time Easy to track progress Easy to identify bottlenecks 2. Approval Requests Approval requests get manager or department approval without leaving the ticketing system . Examples: Hardware requests: Manager approval before equipment purchase Budget requests: Finance approval before expense processing Access requests: Security or manager approval before granting access Benefits: Approvers notified automatically Approval history captured No separate email chains Faster approval cycles 3. Action Flows Action flows automate updates in external systems . Examples: HR systems: Update employee records when onboarding completes Asset management: Record hardware assignment Messaging platforms: Notify requestor when work is complete Benefits: No manual data entry across systems Consistent data across platforms Reduced risk of errors End-to-end automation How They Work Together When an employee submits a new hire onboarding request : Task list defines the steps: create account, assign equipment, provision access, schedule training Approval request routes to HR manager for approval Action flows create the account in HR systems, assign equipment in asset management, send notifications The Automation Hierarchy Level Description Example Manual Agent does everything by hand Agent creates account, assigns equipment, updates systems Task List Agent follows a checklist Agent follows predefined steps for onboarding Approval Workflow Approvals routed automatically Manager approves hardware request Action Flow Systems updated automatically HR system updated when onboarding completes Full Automation End-to-end automation Request → approval → fulfillment → notification with no manual steps Benefits Benefit Impact Consistency Every request follows the same process Speed No time wasted figuring out what to do Accuracy No steps missed or skipped Traceability Clear record of who did what when Scalability Processes work the same at any volume Playbooks: The Next Evolution Atlassian has introduced Playbooks as a feature that combines task lists, approvals, and action flows into a single, guided experience. Each playbook can include : Instructional steps: Clear instructions for manual actions agents must take Automation steps: Tasks that are automatically executed by the system This ensures that every agent follows the same process, which is especially useful for high-volume or critical requests. It also aligns perfectly with ITIL4's focus on standardization and automation to improve reliability and speed. Conclusion: Stop Building from Scratch Task lists, approvals, and action flows transform service request fulfillment from an ad-hoc process into a standardized, automated workflow. Organizations can stop building from scratch and start using predictable, repeatable patterns for common requests. Action Items for Your Organization Identify your 5 most common service request types Document the steps for each Build task lists for these request types Set up approval workflows where needed Create action flows for external system updates Start with one request type, then expand  

From IT to Facilities — Why Service Request Management Is the Key to Workplace Experience The Rise of Facilities Service Requests Facilities services have become a core component of enterprise service management. Employees need: Transportation and parking Room booking Facilities tickets (maintenance, cleaning) Office equipment and supplies Lobby services Maps and wayfinding The Facilities Challenge Historically, facilities requests were handled through separate systems or ad-hoc processes. This fragmentation created a poor employee experience: Problem Impact Separate system for facilities Employees don't know where to go No tracking or visibility Employees don't know request status Inconsistent response times SLAs don't exist or aren't tracked Siloed operations No connection to IT, HR, or other services The Unified Approach Microsoft's Employee Self-Service Agent includes real estate and facilities as a key vertical, handling requests for: Transportation Dining Room booking Lobby services Facilities tickets Parking registration Maps  The previous experience was fragmented across mobile, websites, and physical kiosks. The new agent unifies these experiences in one place . Benefits of Unified Facilities Service Management Benefit Description Better employee experience One place for all needs Faster resolution Standardized processes and SLAs Better tracking Visibility into request status Data-driven improvements Analytics on request patterns Cross-department coordination Connected to IT, HR, and other services Facilities Service Request Types Category Examples Workplace services Desk booking, office moves, space requests Maintenance Repairs, cleaning, temperature issues Equipment Furniture, office supplies, technology Transportation Parking, shuttle service, travel Facilities access Building access, key cards, security Conclusion Facilities service requests are a growing part of enterprise service management. Organizations that include facilities in a unified service delivery model will deliver a better employee experience and operational efficiency. Action Items for Your Organization Map current facilities request process — what's fragmented? Identify the most common facilities requests Integrate facilities into your service management platform Define SLAs for facilities request types Measure employee satisfaction with facilities services  

Why Fragmentation Is Killing Your Service Request Management — And How to Fix It The Fragmentation Problem Collecting and managing all service requests in one place is essential to avoid duplicate work and provide employees with a central location for help . Yet many organizations still have separate processes, tools, and portals for different departments. Why Centralization Matters The Employee Perspective Employees don't want to remember which system handles which request. They want one place to go for everything . The Operational Perspective Fragmentation creates duplicate work, inconsistent processes, and poor visibility. Centralization gives a bird's-eye view of all requests — including status, timeline, and owner — and enables better tracking and reporting . Steps to Centralize Request Management 1. Map the Current Landscape Identify all current request entry points — portals, email, chat, phone, walk-ins. Document what types of requests go where. 2. Define a Unified Entry Point Create a single portal for all service requests. This doesn't mean every request is handled the same way — it means every request starts in the same place . 3. Build Cross-Department Workflows Requests that span departments should flow automatically between teams . Users shouldn't need to know which department handles which request. 4. Unify Reporting With all requests in one system, you can see the full picture — volume trends, resolution times, satisfaction scores across all departments. 5. Communicate the Change Tell employees: "All service requests now start here." Make it clear and simple. Benefits of Centralization Benefit Impact One place for employees No more guessing which system to use Complete visibility See all requests in one place Consistent experience Same interface across departments Better tracking Request status visible to all Clearer reporting Complete data for analysis Conclusion Centralization is the foundation of effective service request management. Without it, you have fragmented processes, frustrated employees, and poor visibility. With it, you have a single, consistent, trackable system for all service needs. Action Items for Your Organization Map all current request entry points Identify duplicate and fragmented processes Define a single portal for all service requests Build cross-department workflows Communicate the change to employees Measure the impact on efficiency and satisfaction