Skip to content

Change management flow

Below are the 4 key stages which we’d like to put all our significant changes through, namely: Hold, Assess, Trial and then Adopt.

Here is a bit more about these:


This represents things we seriously consider using as an agreed practice throughout the organization. We don’t say that you should use these for every project; any tool should only be used in an appropriate context. However, if there is a relevant use case then we strongly recommend that you use the ones in ‘Adopt’.

Example: Next.js, Prisma


This comprises of things we think are ready for use, but not as completely proven as those in the Adopt ring. We think of applying these things on a trial basis, to decide whether they should be part of our toolkit/workflow. Using these on a client or a production environment requires senior oversight and support.

Typically, something will “graduate” from this into Adopt when we have a clear end-to-end application of a tool/workflow/process ready and documented. This doesn’t have to be a final version or a final form of evolution/perfection. This can be gradual. Like an MVP (Minimum Viable Product).

Example: Cypress, PHP_CodeSniffer WordPress Coding Standards, WordPress deployment and environment sync strategies

Other times, things like Tailwind CSS will prove that they have specific applicability but might not be ready for full-scale adoption - and hence moved to Hold. Doesn’t mean it is bad, familiarity/knowledge is great, and so is recognizing the limits/scalability.


This consists of things to look at closely, but not necessarily trial yet - unless you think they would be a particularly good fit for our clients and/or teams. These are things we feel are interesting and worth keeping an eye on.

For example: Redux Toolkit


This can contain this thing that is even though widely accepted in the industry, or has a big enough buzz around or lot so of anticipation - we haven’t had a good experience with or don’t see broad enough applicability to our clients and team members.

For example: Gastsby boilerplate or Partytown


To drop/list out all our ideas/blips/things we see or things we want to discuss with others around us.

If you have any questions, thoughts or suggestions then feel free to engage in a conversation here, or on the full roadmap here: Technology Roadmap.

If you see us jumping/skipping this, we welcome you to guide us through this process. More importantly, if you see something missing from the list and want to put it on our radar, then please add/share!