Design and scoping as part of implementation

The problem

Once a problem is already identified, order handling, quote preparation or management reporting for example, the next mistake is to start building straight away. Nobody has yet written down where the data comes from, in what form, who approves changes, and what stays out of the first version. Without this work the build drags on, or solves the wrong part.

This isn’t a separate assessment product or a free study. It’s the first, paid phase of an implementation project, and we only do it once the implementation is already decided or under serious consideration.

What we do

We go through the current state of the work process together with the people who do it: where the data comes from, in what form it exists, and where the finished result needs to go. We identify the system connections needed and check their availability.

We scope the content of the first version and what stays outside it. We agree responsibilities: who approves the result, who owns it after go-live, and which decisions always stay with a person.

The work ends with a decision point. You get a scoped, written description of what will be built, before building starts. If the scoping shows the solution isn’t worth it, or that the data it needs isn’t available, that’s also a valid outcome: building doesn’t continue without a separate decision.

What you own

The scope and the design document you can start the implementation from. They stay with you the same way the rest of the implementation’s documentation does, as part of the same project.

What we don’t promise

  • A free or separate assessment ahead of a known problem. Design and scoping happen as part of an agreed implementation, not as a separate first step offered to everyone.
  • An open-ended study. The content and timeline are agreed in advance, like every other phase of the project.
  • A finished system at this stage. This phase produces a decision and a scope, not an implementation.
  • That every identified need is worth building. Some scoping work ends with the conclusion that nothing should be built, and that’s a recorded outcome too.

First step

Tell us which implementation project this is. We’ll agree what the design and scoping phase covers for this particular project.

Get in touchNext step: Implementation projects: automations and agents

Next

Get in touch

The easiest way is a WhatsApp message. Tell me which task in your company repeats, or what kind of training your team needs. I reply within a working day.

Väinö KaalikoskiCEO

WhatsApp: +358 44 5088 112Phone: +358 44 5088 112Email: vk@ptg.fi