3 to 6 monthsTypical delivery time for IT requests requiring network changes
Weeks to monthsDuration of discovery meetings between IT clients and IT groups
MonthsSaved in lost opportunity & operational cost via self-service
The Typical Process Model
Generally, the IT clients think that requesting IT services, specially which requires network changes, takes about 3 to 6 months to deliver. The typical process model is:
- IT Clients and IT groups conduct various discovery meetings, goes from many weeks to months.
- IT group start a mini-project to track the request to delivery.
- IT Clients are either updated through meetings or otherwise don't see visibility on progress except target delivery date.
- In some cases, the steps from '1' to '3' goes through multiple iterations as requirement changes.
- There is limited way to track transparently what was requested vs what is implemented on network.
IT groups can offer self-service experience to IT clients for standard services and save months in lost opportunity & operational cost.
Self-Service for Standard Services
All this is even true for cases when IT groups can offer some of these engagement-requests as a standard service and do not need to even go through this long back-n-forth engagement process. IT groups can offer self-service experience to IT clients for standard services and save months in lost opportunity & operational cost. For example:
- Activate/deactivate company partners to connect with company's corporate network
- Add/Update voice, video, data services to office (branch, remote, sales, campus offices)
- Add/Update/Delete extranet partners access to apps running in private data centers
- Enable hybrid-cloud model for Apps team to seamlessly & securely connect with public-clouds
- Change QoS (quality of service) on existing office setup
- Change WAN connectivity providers based on service quality SLAs
- Many more…
Learn More
If you are interested to know how blaZop platform can help?
Long Engagement vs Self-Service
The long wayThe blaZop way
Time to deliver3 to 6 monthsstandard services delivered without the long engagement cycle
DiscoveryMeetings spanning weeks to monthsrequest standard services directly, no back-n-forth
TrackingMini-project per request, visibility limited to a target datetransparent view of requested vs implemented
IterationsSteps repeat as requirements changeclients make standard changes themselves
CostMonths of lost opportunity & operational costthose months saved
What to remember
- IT clients expect requests requiring network changes to take about 3 to 6 months to deliver under the traditional engagement model.
- The typical process — discovery meetings, mini-projects, and repeated requirement iterations — offers little visibility beyond a target delivery date.
- There is limited way to track transparently what was requested vs what is implemented on the network.
- Many engagement requests could be offered as standard services, skipping the long back-and-forth entirely.
- A self-service experience for standard services (partner connectivity, office voice/video/data, extranet access, hybrid-cloud, QoS, WAN provider changes) saves months in lost opportunity and operational cost.
