Project method: 6 steps proven across 500+ mandates.

Frequently asked questions

Frequently asked questions about our method.

Can't find your answer? write to us.

• Do the six steps apply to a small engagement?

  Yes, but compressed. On a 20-hour engagement, assessment and planning fit into one meeting and a one-page document. What does not change, whatever the size: the documentation delivered at the end, and the fact that you own it.

• How long does the assessment step take?

  One to two weeks for an environment under 200 users, three to four for a multi-site organization. It produces a quantified picture of the current state and a priority list — deliverables you can use even if you don't continue with io4.

• Who runs the project day to day?

  A named io4 project lead, plus the technical specialists brought in. You get a single point of contact for progress and budget, and direct access to the experts on technical questions — without going through a service desk.

• What tracking tools do you use?

  Microsoft Project for the schedule, Azure DevOps for technical tracking, Teams for day-to-day collaboration. Follow-up is weekly by default, with a governance review each quarter on recurring engagements.

• What does the delivered documentation contain?

  The target architecture, the configuration decisions and the reasoning behind them, the operating procedures, and the access. The goal is that another team could take over the environment without us — that is what separates a deliverable from a dependency.

• Do you train our teams at the end of the project?

  Yes, that is the fifth step. Training is built per persona — leadership, IT, end users — rather than as a single generic session, because the three audiences have neither the same questions nor the same time available.