Category: Change

June 2014 · Change, Collaboration, ITSM, Knowledge

The ITSM Review named ITinvolve Service Manager “Best in Class” in its independent comparative analysis of Change, Configuration and Release solutions. The reviewer highlighted our breakthrough approach: connecting trusted knowledge and the right experts to every change, so risks surface before a change is made — not after it breaks production.

Unlike traditional tools that route approvals through people who lack context, ITinvolve engages stakeholders based on what they own and what they know, and puts the full dependency picture in front of them before they decide.

What’s Your Discipline?

March 2014 · Change

IT work spans many disciplines — change, release, configuration, asset, automation — but the information they need lives in the same environment. Discipline-by-discipline tools create silos: each team sees its own slice and nobody sees the whole.

We look at how a shared, peer-reviewed view of your environment serves every discipline at once — so a change manager, a release engineer, and an asset specialist work from the same trusted picture instead of three conflicting ones.

5 Problems With the IT Industrial Revolution

January 2014 · Change, Collaboration

Industrializing IT — standardizing, automating, optimizing for flow — sounds efficient, but applied blindly it amplifies five classic problems: changes that collide, knowledge that never leaves people’s heads, dependencies nobody mapped, automations nobody owns, and teams optimized for their silo instead of the service.

Published in APMdigest

The Ends Justify The Work

December 2013 · Change, Collaboration, Knowledge

A story about goals: a company where every team works hard, yet changes still collide and releases still slip — because the work is aligned to tickets, not outcomes. Connecting daily IT work to the business goals it serves changes what gets prioritized, who gets engaged, and how change risk is judged.

When teams can see how their changes ladder up to delivering products, servicing customers, and improving quality, conversations shift from “is this ticket done” to “does this change move us forward safely”.

Knowledge Isn’t Free and Neither Are the Donuts

November 2013 · Change, Collaboration, Knowledge, Social IT Maturity

Tribal knowledge feels free until the person who holds it leaves, goes on vacation, or simply isn’t in the room when a change is approved. Then the cost shows up as failed changes, longer outages, and decisions made on guesswork.

We make the case for treating knowledge capture as part of the work itself — reviewed by peers like code, connected to the systems it describes, and surfaced automatically when the next change touches them.