Within the work processes drawn in the previous stage, tasks AI can automate and tasks it cannot are mixed. The first task of system design is determining which tasks AI will handle, whether to build them internally or procure them from the market, and in what priority and stages to adopt them. Attempts to change everything at once almost invariably fail. A phased approach that starts with areas that can show visible results quickly, while simultaneously building organizational trust and data assets, is much more stable. HCG prepares a priority matrix considering both the magnitude of impact and implementation difficulty, distinguishing short-term quick wins from strategic investment areas, and presents a phased adoption roadmap spanning 6 to 24 months. Simultaneously, it differentiates between areas where in-house building is rational and areas where using market-validated solutions is rational — based on domain specificity, data sensitivity, and differentiation contribution — providing the basis for decision-making. It also designs integration scenarios with HCG's own solutions (elizax · hunel · JaDE · talenx) so that consulting outputs are not buried in separate systems but can be directly reflected in actual operating tools. Even when integration with external solutions is needed, the integration method and data exchange approach are pre-defined to minimize post-adoption operational burden.
HCG builds a priority matrix that weighs both impact and implementation difficulty, distinguishes Quick Wins from strategic investment areas, and proposes a 6- to 24-month phased adoption roadmap.
At the same time, we separate areas where building in-house makes sense from those where leveraging market-proven solutions makes sense — using criteria such as domain specificity, data sensitivity, and differentiation contribution — to provide the evidence decisions require.
We also design integration scenarios with HCG's own solutions (elizax · hunel · JaDE · talenx), so consulting outputs aren't siloed in a separate system but feed directly into the operational tools that get used. Where external solutions need to connect, we define the integration approach and data-exchange method up front to minimize operational burden after launch.