Delivery withoutcreativity is justexecution. I do both.
I build and deliver digital projects. From raw idea to shipped product. Consistent quality, creative problem-solving, real ownership. Not a PM. A project creator.
8 years in digital.
Every project taken on has shipped.
No abandoned work. Ever.
Complex projects. Consistent delivery.
What I actually do
Not a title. A way of working. Ideas taken seriously, delivery taken seriously, at the same time.
01
Project Delivery
End-to-end ownership of complex digital projects. From requirements through build, QA, UAT, and release. Multiple teams, vendors, stakeholders, all moving together.
02
Product Building
Taking an idea from concept to a real, shipped product. I help structure what to build, in what order, and drive the execution until it exists in the world.
03
Process & Workflow
Finding where things slow down and building the systems that fix it. Not process for the sake of process. Structures that actually make teams faster.
04
AI & Automation
Embedding AI tools into real team workflows. Not theory. Practical adoption that turns unused licences into actual productivity gains.
Consistency is not enough. Neither is creativity. The job is both, at once.
Most delivery problems aren't technical and most creative problems aren't about ideas. They're about ownership. Someone who takes both seriously and doesn't drop either one when things get hard.
I'm Giannis Lazarou. 8+ years delivering digital projects across agencies and enterprise. Professional Scrum Master II, Agile Coach, and someone who still thinks the best delivery is the one that ships something worth shipping.
// work
Web Banking Platform Redesign, Banking Sector
A platform redesign 6 months behind schedule. No coordination layer, no single owner. A structural intervention that got it delivered.
7 teams, 10 departments, 2 external vendors. Scope drifting, budget bleeding, no visibility. The challenge: establish structure mid-project without stopping delivery.
Banking
Sector
7 teams · 10 dept · 2 vendors
Complexity
Delivered on time
Outcome
Have something you want to build or fix?
I work with digital agencies and product teams. If you have a project that needs real ownership, reach out.
A platform redesign 6 months behind. Delivered on time.
A major bank commissioned a full redesign of their web banking platform. Planned for 6 months. By the time the project was picked up, 12 months had passed and nothing had shipped. Seven teams working in parallel with no coordination layer. Two external vendors outside any governance structure. Scope drifting. Budget bleeding with no visibility. The challenge: establish structure and ownership mid-project, without stopping delivery.
Client
Banking Sector, Greece
Focus
Delivery Recovery · Governance · Coordination
Scale
7 teams · 10 departments · 2 vendors
Outcome
On time. Budget contained.
// when the project was picked up
12 months in, 0% delivered
7 teams with no coordination layer
Scope changing with no impact process
2 vendors with no governance
Budget overrunning, no visibility
No single person accountable
// when it shipped
Delivered on the revised date
7 teams moving in the same direction
Single backlog, clear owners
Both vendors under project governance
Budget overrun stopped and contained
Real-time reporting to all 10 departments
0mo
Behind schedule when picked up. Project had already doubled in time.
0
Stakeholder groups needing alignment across teams, departments, vendors.
Shipped
On the revised date. No further delays. Budget overrun stopped.
It didn't turn around with one decision. It turned around with structure applied consistently.
month 0, before
Crisis, no owner
Teams in silos. Vendors unmanaged. Scope unclear. Budget bleeding. Nobody with a mandate to make decisions across all workstreams.
week 1–2
Full audit: map reality, not the plan
Mapped all workstreams, vendor contracts, and the actual backlog. Found the 5 blockers stopping everything. Daily syncs across all teams from day one.
month 1
Build the coordination layer
Scope boundaries defined. Clear ownership per workstream. Vendors inside governance. Single prioritised backlog. Scope change process in place.
month 2–3
Teams start moving
Structure in place, teams stopped waiting for decisions. Blockers resolved in hours. Delivery velocity picked up across all workstreams.
final
Delivered. On time.
7 teams, 10 departments, 2 vendors. Same finish line, same date. No further budget escalation.
Give people clarity and they ship. The job is to build that clarity, not manage a spreadsheet.' data-gr='Τα περισσότερα delivery failures δεν είναι τεχνικά. Είναι δομικά. Δώσε στους ανθρώπους ξεκαθάρισμα και παραδίδουν. Η δουλειά είναι να χτίσεις αυτό το ξεκαθάρισμα, όχι να διαχειρίζεσαι ένα spreadsheet.'>Most delivery failures aren't technical. They're structural. Give people clarity and they ship. The job is to build that clarity, not manage a spreadsheet.
Own it explicitly
Without one accountable person, every decision gets delayed. First step: make clear that person is you.
Structure before speed
Slow down for two weeks, build the structure, then let teams accelerate. Rushing without structure just burns more time.
Visibility ends overruns
Budgets overrun in the dark. Weekly reporting to all stakeholders creates accountability without policing.
Recognize this? Let's talk about your project.
Let's figure out if I can help.
No pitch. Tell me what you're working on. I'll tell you if it's something I've seen before and what I'd do about it.