GlideQuest Consulting — home GlideQuest Consulting — home

How I can help

I work best embedded in a platform team, with access to the instance and to the people who depend on it. Rather than sell packaged engagements, I take on contract work for as long as it needs and stay flexible about the shape it takes. The three areas below are where I spend most of my time.

Development & administration

Additional senior capacity on your platform team: scoped application development, integrations, upgrades, and the routine administration an instance needs. I work directly in your instance, alongside your developers.

In practice this tends to mean finishing a stalled module or integration, CMDB and CSDM assessment and remediation, providing cover while your ServiceNow administrator is out, or handling the upgrades, clone-downs, and instance scans that implementations rarely plan for. I work in both configuration and code, and will tell you which of the two a given problem actually calls for.

Architecture & platform ownership

I have held the platform owner role, not only the developer one. Roadmaps, governance, technical design, and the decisions that keep a platform consistent as it grows. Available on a fractional basis where a full-time owner is not warranted.

This might be an instance health check assessed against what the platform is actually being asked to do, intake and development standards scaled to the size of your team so that they get followed, a 90-day roadmap that stays with you either way, or a review of a partner's proposed design before you sign it off.

Requirements, backlog & advisory

Turning a loosely defined request into work a development team can pick up. Discovery with your stakeholders, epics and stories with acceptance criteria, or a review of a proposed design before you commit to it.

That usually starts with working sessions to establish the outcome you are after and what "done" needs to look like. From there the work is broken into epics and stories with acceptance criteria written clearly enough that a developer can start without a meeting first, sequenced by value and dependency, with assumptions and open questions recorded while they are still inexpensive to answer. What happens next is your call: we can build it together, or you can take the backlog to your own team.

How engagements usually work

Arrangements are shaped around what you need rather than picked off a menu. That might be a block of hours for a problem you can already describe, a fractional arrangement where you want a senior resource on the platform on an ongoing basis, or a defined project with a scope and deliverables that stay with you. The commitment flexes with the work — more of it when there is more to do, less when there is not. All of it is remote, carried out in your instance, and visible to your team as it happens.

If you are not sure which of those fits, that is fine. Working out the shape of the engagement is part of the first conversation.

Tell me what's going on with your platform.

The first step is a 30-minute conversation about what you need. No charge, and no obligation to go further.

Start the Conversation