Freshservice / ITSM
Designing and improving service-management systems so complicated organizational processes become understandable, maintainable workflows.
A generalized account of enterprise platform work. Diagrams illustrate design principles; they do not represent an employer's systems or configuration.
PLATFORMS / AUTOMATION
Problem
Service platforms accumulate complexity one request at a time. Similar forms drift apart, fields mean different things in different places, and requesters are asked to make decisions that belong to the fulfillment team. The engineering problem is to preserve the information operations needs while making the service understandable to the person asking for it.
Approach
Start with the requester: what are they trying to accomplish, and what can they reasonably know? Work with the people who request, approve, fulfill, and support a service to separate those needs from implementation details. Consolidate repeated patterns, agree on field conventions and ownership, and make approval and fulfillment logic explicit. Refine the workflow with stakeholders before automating it.
Build
My work spans Freshservice administration and development, service-item architecture, request forms, and workflow automation. I approach the catalog as a maintained interface: consistent fields, conditional questions where they clarify a request, and reusable patterns for routing and approvals. ITAM and CMDB work brings another layer of discipline around ownership, relationships, and the quality of the information a workflow depends on. AI-assisted service management and CMDB experimentation are areas of exploration, not claims of a completed autonomous service platform.
Service catalog architecture
Organize services around requester intent. Consolidate similar items where a shared pattern is clearer, while keeping materially different processes distinct.
Forms and requester experience
Use language people recognize. Ask for the information they can provide, and reveal conditional questions only when those answers affect the service.
Workflow and approval design
Make ownership, decisions, and fulfillment steps understandable. Automate repeatable work with clear handoffs and a path for exceptions.
Platform standards
Keep field conventions, metadata, approval patterns, and ownership consistent so a configuration remains understandable after its original author moves on.
Assets and configuration
Treat CMDB and ITAM maturity as an ongoing data and process problem. Useful relationships need reliable ownership and maintenance practices.
AI-assisted service management
Explore how AI and knowledge can support service work. Evaluate usefulness and oversight before allowing an experiment to become an operational dependency.
Technologies
- Freshservice
- ITSM
- ITAM
- CMDB
- Workflow automation
- AI-assisted service management
Outcome
The areas of impact are a simpler requester experience, less duplication in service design, clearer operational handoffs, and patterns that are easier to maintain. Standards also create a stronger basis for automation and for improving asset and configuration data over time. This account describes the direction and value of the work without publishing internal measures or attributing outcomes to a specific employer implementation.
Conceptual visuals
Request lifecycle
An illustrative sequence of responsibilities, not a configured production workflow.
- 01Requester
- 02Service item
- 03Validation
- 04Approval
- 05Workflow
- 06Fulfillment
Platform relationships
A conceptual view of how service design connects to automation and operational information.
- 01Service catalog
- 02Workflows
- 03Automation
- 04CMDB / assets
- 05Reporting
From variation to a reusable pattern
Consolidation is useful when it preserves the distinctions that matter to the service.
- 01Fragmented requests
- 02Shared intent and fields
- 03Standardized service patterns
What I learned
- The requester should not need to understand how the service is implemented.
- A service catalog is an interface, not an inventory of every possible request variation.
- Standards make changes easier to reason about across the platform.
- Automation magnifies the process underneath it. Clarify the process first.
- Platform engineering includes organizational decisions: ownership, exceptions, and how teams work together.