Skip to content

STORIES · TECHNOLOGY & SERVICES

In technology, advantage does not come from technology alone.

It emerges when capabilities, process, security and accountability for results come together in a model that can scale without proportionally scaling complexity.

Transformation does not always happen in a factory.

In technology and services businesses, the product may be knowledge, expertise, a project, information or a decision.

That changes the mechanics of scale.

Having great experts is not enough. Their knowledge must also become a repeatable process, service, project and result for the client.

Technology becomes scalable only when the way it is delivered becomes scalable too.

7 STORIES

SERVICES & CAPABILITIES

P&L · PMO · SOC · KSC · AI/ML · DELIVERY

How to scale capabilities without scaling chaos

CONTEXT

A technology integrator operating across IT infrastructure, professional services, cybersecurity and SOC, cloud, ERP/BPM, automation, AI/ML and transformation projects.

PROBLEM

Product sales can be scaled through volume. Scaling services, projects and expert knowledge is harder. Dependencies emerge between sales, presales, delivery, PMO, expert availability, resource utilization, costs and project profitability. At the same time, market value is shifting from delivering technology towards solving business problems, cybersecurity and accountability for outcomes.

CHANGE

Moving from a model centered on transactions and individual capabilities towards a more consultative end-to-end model. Development of a portfolio including cybersecurity and SOC, solutions supporting KSC requirements, AI/ML and automation. In parallel, clearer accountability, governance, pipeline management, PMO, KPIs and the economics of sales and project delivery.

MY ROLE

C-level responsibility for operations and transformation of the operating model, connecting strategy, sales, delivery, technology, processes and P&L.

RESULT

Technology capabilities were connected to a repeatable way of identifying problems, designing solutions, delivering projects and managing their economics.

ADVANTAGE

Scaling knowledge and client value without proportionally scaling organizational complexity.

FROM THE PROJECT

For one organization, a SOC is the consequence of cybersecurity maturity. For another, the journey begins with regulatory requirements, including KSC.

But once an organization truly starts seeing its infrastructure, effects emerge that nobody originally asked for.

The data provides a better understanding of resource utilization, access, licenses and tools. It also reveals phenomena that had previously remained outside formal control.

One of them was Shadow AI.

An attempt to bring access to unauthorized models under control revealed that some teams had already embedded generative AI so deeply into the way they worked that restricting it had an immediate impact on productivity.

Cybersecurity revealed more than technology risk. It also revealed how deeply AI had already changed the organization's real way of working.

IN THIS PROJECT

  • Strategy
  • P&L
  • PMO
  • Delivery
  • SOC
  • KSC
  • AI/ML
  • Cybersecurity
NEXT STORY02 DATA AND PROCESSES IN FMCG

DATA AND PROCESSES IN FMCG

ERP · WMS · MES · SCM · INTEGRATION

Why transformation cannot be run entirely from a meeting room

CONTEXT

A global FMCG manufacturer operating at significant scale, with strong requirements around production continuity, quality, product traceability, logistics and precise cooperation between enterprise systems.

PROBLEM

In this industry, every digital process has physical consequences. Data has to reflect the actual flow of materials, production, warehousing and distribution. An error in the system does not remain an error in the system. It can become a production, logistics or quality problem.

CHANGE

Connecting business and production processes through ERP, WMS, MES and SCM solutions, and integrating the technology environment with the way the plant actually operates.

MY ROLE

Managing transformation projects in the client's environment, connecting business, process and technology requirements and translating them into working solutions.

RESULT

Technology became embedded directly in the real flow of products and information instead of operating as an independent IT layer.

ADVANTAGE

A digital process creates value only when it works just as well in the system as it does on the factory floor.

FROM THE PROJECT

Sometimes digital transformation enters the production environment very literally.

After months of working inside a global FMCG manufacturer's plant, the smell of the product was no longer limited to clothing.

After each visit, clothes needed a thorough wash. Even the laptop needed airing out.

Technology may be digital. A transformation project always happens in the very physical reality of a business.

IN THIS PROJECT

  • ERP
  • WMS
  • MES
  • SCM
  • Production
  • Logistics
  • Integration
NEXT STORY03 BANKING & FINANCIAL SERVICES

BANKING & FINANCIAL SERVICES

BIOMETRICS · SECURITY · IDENTITY · INTEGRATION

Even the most digital process still ends with a human

CONTEXT

A global financial services environment with demanding requirements for security, user identification, data integrity and process reliability.

PROBLEM

In banking, technology operates in an environment with extremely low tolerance for error. A process must be secure, compliant, scalable and usable under real-world conditions, not only in an ideal scenario.

CHANGE

Integration of digital authorization and user identification solutions using biometrics, with the process adapted to actual operating conditions.

MY ROLE

Leading the project at the intersection of technology, process and user experience, and identifying constraints that emerged only when the solution was used in practice.

RESULT

The technology process was adapted to the real conditions in which people worked instead of expecting reality to adapt to technology.

ADVANTAGE

Security works when people can use it without having to work around the process.

FROM THE PROJECT

Biometrics looked perfect on the process diagram.

The problem appeared only in a branch serving employees of a large manufacturing plant.

The fingerprint reader needed a readable fingerprint. Employees coming off a production shift did not always have one.

So the digital identification process needed a very analogue step: wash your hand.

Practice quickly optimized even that. Because it turned out that washing just one finger was enough.

Even the most digital process ends with a human. And humans do not always behave the way the diagram predicts.

IN THIS PROJECT

  • Banking
  • Biometrics
  • Identity
  • Security
  • Integration
  • Processes
  • Operational UX
NEXT STORY04 TRADE & LOGISTICS

TRADE & LOGISTICS

WMS · AUTOMATION · ROBOTICS · DATA

What happens when technology evolves faster than the rules around it

CONTEXT

One of Poland's early fully robotized high-bay warehouse environments, handling products with short shelf lives.

PROBLEM

The system had to do more than know where each product was located. It had to continuously manage inventory rotation so that batches with the shortest remaining shelf life were dispatched first. Once the technology problem had been solved, another constraint emerged: regulation.

CHANGE

Warehouse automation, integration of product-rotation logic with WMS and design of a process accounting for both the capabilities of robotics and regulatory requirements governing its operation.

MY ROLE

Managing a project integrating the logistics process, warehouse system, automation and regulatory constraints.

RESULT

The physical and digital processes were integrated into a single automated mechanism for inventory management and product rotation.

ADVANTAGE

Automation can exploit the speed of technology only when processes and the surrounding organization can keep up.

FROM THE PROJECT

Technology successfully handled automatic product rotation according to shelf life.

Then a much harder problem appeared.

Regulations required a machine operator to be present.

A human therefore had to formally participate in a process that no longer required human action. Worse, the robot's speed had to be limited to a level the operator could actually observe.

At full speed, the recruitment pool would probably have needed to include fighter pilots.

Automation reached its technological limit faster than regulation noticed that a human was no longer required to operate it.

IN THIS PROJECT

  • WMS
  • Robotics
  • Automation
  • Logistics
  • Data
  • Integration
  • Processes
NEXT STORY05 IT/OT CONVERGENCE IN HEALTHCARE

IT/OT CONVERGENCE IN HEALTHCARE

HIS/RIS · PACS · HL7 · DICOM · IT/OT · BMS

How to make a CT scanner visible to the system before it stops working

CONTEXT

A multi-site hospital with extensive diagnostic imaging capabilities. HIS managed patient flow and clinical orders, while diagnostic devices operated in separate worlds of manufacturers, service organisations and technical connections.

PROBLEM

The system knew that an examination had been ordered, but not whether the device was actually available. A failure could become visible only after the patient had already been prepared, while technical maintenance remained disconnected from the clinical process.

CHANGE

The clinical and technical layers were connected: HIS/RIS, PACS, modalities, HL7 and DICOM together with OT monitoring covering devices, power supply, cooling and access control. A common view of asset availability, utilisation, service events and maintenance cost was created.

MY ROLE

Integration architecture, medical network security model and coordination between IT, technical teams, clinical staff and equipment manufacturers' service organisations. From concept through implementation to operational handover.

RESULT

Examination planning began to reflect the actual availability of equipment. For the first time, the hospital could see the real utilisation of its most expensive diagnostic assets and manage manufacturer SLAs using its own data.

ADVANTAGE

Higher availability of critical diagnostic assets without automatically resorting to another capital equipment investment.

FROM THE PROJECT

The hardest problem was not HL7 or DICOM.

During integration, we discovered a manufacturer's remote-service connection that had been operating for years without the knowledge of either IT or the data protection officer.

Sometimes integration starts not by creating new connections, but by discovering the ones that already exist.

IN THIS PROJECT

  • Strategy
  • HIS/RIS
  • PACS
  • HL7
  • DICOM
  • IT/OT
  • BMS
  • Cybersecurity
  • Network Segmentation
  • BI
NEXT STORY06 BUSINESS CONTINUITY AND SECURITY

BUSINESS CONTINUITY AND SECURITY

BUSINESS CONTINUITY · HIS · IT/OT · NIS2 · BIA

How to plan for the day when HIS stops working before that day arrives

CONTEXT

A healthcare organisation operating continuously with fully electronic documentation and a complex environment of systems, integrations and devices with very different technology lifecycles.

PROBLEM

The organisation had backups and procedures, but had never tested under realistic conditions how long it would actually take a clinical department to resume operation. Additional risk came from medical equipment running unsupported systems that could not simply be upgraded.

CHANGE

Dependencies between clinical processes and infrastructure were mapped, legacy devices were isolated, critical paths made redundant and monitoring extended across IT and OT. In parallel, a procedure for operating without the core system was created and tested on an actual hospital department rather than merely documented.

MY ROLE

Business impact analysis, resilience architecture and translating regulatory requirements into operational and budget decisions. Leading recovery tests and agreeing with management the level of continuity the organisation was prepared to maintain.

RESULT

Recovery time stopped being a declaration and became a measurable parameter. Legacy devices became controlled exceptions with assigned ownership, while management gained a view of risk expressed in terms of impact on clinical processes rather than the number of vulnerabilities.

ADVANTAGE

The ability to operate on the day something actually fails - and to prove that capability before it is needed.

FROM THE PROJECT

During a recovery test, the critical weakness turned out not to be the backup or the network connection, but an identification-wristband printer connected to a single workstation without guaranteed power.

Without the wristband, the clinical process could not start.

Business continuity rarely breaks where the most attention has been invested.

IN THIS PROJECT

  • Strategy
  • Business Continuity
  • HIS
  • IT/OT
  • Cybersecurity
  • NIS2
  • BIA
  • Disaster Recovery
  • Segmentation
  • Governance
NEXT STORY07 REMOTE EXPERT, LOCAL TECHNICIAN

REMOTE EXPERT, LOCAL TECHNICIAN

AR · PLM · PDM · ERP · WMS · REMOTE ASSISTANCE

How to move an engineer's knowledge to where the engineer cannot go

CONTEXT

A manufacturer of specialized equipment for military and civilian customers. Contract-configured products with high unit value and long life cycles, operating also in locations where local service support and reliable connectivity are not available.

PROBLEM

Service required more than technical knowledge. It required certainty about the exact unit and revision being serviced. Incorrect documentation, lack of a spare part or even a seemingly simple task could stop the equipment until an expert arrived. Support, documentation, product history and spare-parts logistics operated as separate processes. The person in the field had one problem and one pair of hands.

CHANGE

A single service-event workflow was created in which augmented reality became an interface to knowledge and process, not the goal of the implementation. The system identified the exact unit, retrieved its configuration from PLM and the correct documentation revision from PDM, then guided the technician step by step through the procedure. When expert knowledge was required, a remote session was launched with both sides seeing the same image. Spare-part demand was created directly from the procedure and connected to ERP and WMS, including the ability to identify an approved alternative solution. The entire process was also designed to work offline.

MY ROLE

Concept and solution architecture, including the data model linking the unit, configuration, documentation and service event, as well as integration of PLM, PDM, ERP and WMS. Defining together with engineering, quality, service and security the boundary between tasks that could be performed independently, tasks requiring remote support and tasks requiring direct expert involvement. From concept to implementation.

RESULT

Some activities that previously required an expert to travel could now be performed locally using documentation specific to the exact unit. The service history began to be created in real time, while knowledge from field operations flowed back into product maintenance and development.

ADVANTAGE

Expertise stopped being tied to the physical location of the expert, while technical support stopped scaling with the number of specialists sent on the road.

FROM THE PROJECT

The solution was built for extreme conditions. Its most tangible value appeared in the civilian business.

In some countries the company was unable to maintain an authorized service network. A local technician with basic qualifications could nevertheless perform the repair using step-by-step guidance, with an expert joining only when genuinely required.

Repair quality stopped depending on who happened to be available locally.

Because knowledge can be moved without moving the person.

IN THIS PROJECT

  • AR
  • Remote Assistance
  • PLM
  • PDM
  • ERP
  • WMS
  • Configuration Management
  • Knowledge Management
  • Service
  • Systems Integration

COMMON DENOMINATOR

Different industries. The same accountability for change.

In a technology company, value may come from expertise. In banking, from information and trust. In trade, from flow. In services, from the ability to solve a client's problem.

The technologies differ, but the mechanism remains similar.

Understand the process. Find the constraint. Connect capabilities and technology. Make the change work.

EXPLORE OTHER STORIES

Do not start with technology. Start with the result.

If you see a problem, an opportunity or a change that cannot be addressed with another standard project, let's talk about the result you want to achieve.