By David Bartas · Updated
What this work helps you decide.
Business transformation consulting connects a proposed technology change to the people, processes and delivery work it affects. I help teams define responsibilities, dependencies and review milestones so a strategic direction becomes a plan they can operate and revise.
What has to change around the technology for the new way of working to be usable?
What to bring.
- The business goal and the proposed technology change
- The current process and the teams involved
- Dependencies, constraints and decisions already made
- A proposed timeline and the people responsible for delivery and operation
Typical deliverables.
- A delivery sequence with dependencies and review milestones
- Clear responsibilities for decisions, implementation and operation
- A practical record of open risks, assumptions and next steps
The scope depends on your question and available context. A consultation frames the decision; a complete review, workshop or delivery engagement is scoped and quoted separately.
How I approach the work.
01
Describe the change
Define the intended outcome and map which workflows, systems and people are affected. Distinguish the technical deliverable from the operating change around it.
02
Make ownership clear
Identify who decides, who delivers and who operates each part of the change. Surface gaps where a dependency or responsibility has no agreed owner.
03
Sequence the delivery
Order the work around dependencies and practical release boundaries. Include hand-offs, preparation and review points instead of treating launch as the end of the plan.
04
Review and adapt
Agree which observations will show whether the new process is working. Use those reviews to change priorities and resolve issues with the responsible team.
Related project evidence.
These cases describe project scope and personal contributions. Each links to a public product, profile or source record.
George Business
Aug 2022 – Jun 2025
Payment lifecycle, transaction history and card reservations for Česká spořitelna’s corporate banking.
Read the case study →BankID onboarding
Jun 2021 – Feb 2022
Solution architecture and integration of BankID into MONETA’s web and mobile onboarding.
Read the case study →David Bartas is the founder of Investboard and creator of InvestingStack. His own products and ecosystem work are identified in the case studies.
Common questions.
How is transformation work different from a technology implementation?
Implementation delivers the technical change. Transformation work also considers the workflow, responsibilities, hand-offs and operating practices needed to use it. The scope should make both the technical delivery and the surrounding process change explicit.
Can we begin with a single team or workflow?
Yes. Starting with a defined workflow makes the goal, dependencies and ownership easier to review. A consultation can frame that boundary; workshops and delivery support are scoped separately when the wider change is understood.