My Approach: Turning Talked-About Work into a Working System

When an organization starts an ERP project, it is not only choosing new software. It is testing its process quality, data discipline, decision speed, ownership culture and readiness for change.

An organization may say it is transforming digitally. But if the work still happens in Excel, on the phone, in personal memory or through off-system habits, and is entered into ERP afterwards, transformation has not really happened.

If ERP is used as a helper tool where data is entered after the work is done, the organization has not digitally transformed. Real transformation starts when the work itself moves through the system.

Data should enter the system as close as possible to the point where it is born. Purchase requests, production confirmations, stock movements, quality results, maintenance requests and sales orders lose value if they remain after-the-fact records.

The value of ERP is to bring process, data, responsibility and decision onto the same ground while the work is being done.

In Türkiye, and especially in Anatolian field environments, project work requires understanding the local rhythm, culture and human reality of the organization.

Every organization has a language, every factory has a rhythm, every team has habits, and every region has a way of working. Managing transformation is not only drawing workflows, assigning tasks or preparing timelines.

It means understanding how people decide, what they resist, what they say openly and what they do not say, where the work actually happens and where the data is born.

Organizational change cannot be managed without breathing the dust of the field. Plans that look perfect at the table can break when they meet human reality, organizational habits and decision patterns.

This is why project management, for me, is not only methodology. It is the discipline of reading the environment, touching people, making reality visible and finishing the work.

Every project stakeholder map contains different characters: people who do not listen, people with high ego, people who create negative influence, people who say no by habit, narrow viewpoints, real owners, quiet influencers and people who quietly resist change.

A project cannot be managed by ignoring that reality. Project management is not only timeline, workflow and meeting list; it requires reading human dynamics, the organization’s spirit, stakeholder influence and invisible resistance.

There are many methods, frameworks and ideal models. You need to know them. But in the field, work does not always move in textbook order. Sometimes you do not present the methodology; you carry it in your instinct.

You ask the right question at the right time, bring the right person to the table, make risk visible and create the ground for movement.

The perfect ground for a project almost never appears by itself. A strong project manager does not wait for it; they create enough ground for progress.

My creative production side and my relationship with music taught me to look at projects not only as plans, but also through rhythm, harmony, attention, rehearsal, improvisation and final discipline.

Good work does not come from knowing the right notes alone. It needs rhythm, harmony, rehearsal, listening, knowing when to stay silent and knowing when to step forward.

Projects have a similar truth. Knowing the methodology is not enough; you need to hear the rhythm of the team, the tone of the organization, the tension in the field and the voice of stakeholders.

If everyone in a song tries to step forward at the same time, the music falls apart. If everyone in a project puts their own priority at the center, delivery falls apart. Good management hears every voice but brings the work into a shared rhythm.

Creativity is not lack of planning. Good improvisation requires a strong base. Agility in projects is similar: without preparation, discipline and shared purpose, improvisation produces disorder, not solution.

I look at AI transformation from the same place. AI does not fix a badly designed process; it only makes the disorder visible faster.

If data is dirty, decision mechanisms are weak, process ownership is missing, or user behavior stays outside the system, AI will not solve that magically. It can even scale the gaps faster.

AI can summarize a meeting. The issue is whether that meeting produces decision, action and ownership. AI can prepare a report. The issue is which management decision that report serves. AI can process data. The issue is whether the data was created in the right place, with the right owner, at the right time.

For me, AI is not a miracle replacing transformation. It is a powerful layer that creates value when built on the right data, process, decision and ownership discipline.

The future of project management is not only using more tools. It is preparing smarter decisions, reducing information loss, seeing risk earlier, following action and improving the quality of human decision-making.

The real point is to create value, finish the work and leave a legacy behind.

Finishing a project is not only going live. It means leaving behind a working system, owned processes, people who have learned and a sustainable work discipline.

Go-live is a threshold. Acceptance is a step. Closure is a responsibility. But real success is system usage, process ownership, reliable data and the organization genuinely moving away from old habits.

Every person you do not develop becomes the ground for the same mistakes to repeat in the future. Every resource you consume unnecessarily does not only reduce today’s budget; it reduces tomorrow’s possibilities.

Sometimes the most valuable output of a project is not the system that went live. It is the people who will own it, teams that learn how to decide, a management rhythm that can discuss risk and a repeatable work discipline. That is legacy for me.