Founder & Principal Consultant

Liliana Pettenkofer, founder and principal consultant at Nooqleo

Liliana Pettenkofer

Strategic integrator, operator, and advisor helping leaders turn complex strategy and change into coordinated execution.

How I Got Here

I have always been interested in how the pieces come together.

Long before Nooqleo, I was drawn to organizing moving parts, seeing where something could break, creating structure, and figuring out how people with different responsibilities could move toward the same outcome.

That instinct showed up early.

Growing up in Bolivia and later building a life and career in the United States taught me to navigate different environments, expectations, and ways of communicating. I also found myself creating things from the ground up—including launching a film festival in Bolivia—where ideas only became real if I could organize the people, priorities, resources, and decisions required to make them happen.

Project management became a natural extension of how I already thought: understanding how everything connected and what needed to happen for the work to move.

From Projects to Programs

The work became bigger. So did the questions.

My early career was rooted in marketing, where I learned strategy, campaigns, brands, creative production, and the operational systems behind them.

As the work became more complex, I found myself looking far beyond the original project. More people were involved, more decisions were connected, and what happened in one area increasingly affected what someone else could do.

The questions I was asking changed with it.

Why is this becoming difficult?

What are we missing?

Who needs something they are not getting?

Which decision has not been made?

What is going to become a problem three weeks from now if we do not address it today?

Do we actually have everything in place—and in the right condition—for this work to succeed?

That is where my thinking moved beyond managing a project and toward understanding the environment around it.

Learning From Friction

Good structure only works when people can work inside it.

Some of my most important lessons came from the friction I encountered while trying to improve the work.

You ask more questions. You introduce a process. You change a workflow or shorten a lead time because, on paper, it appears to make perfect sense.

And suddenly someone is frustrated. Or defensive. Or the conversation becomes much harder than expected.

There were moments when I genuinely thought: What just happened?

Those experiences taught me that execution is never only about designing the most efficient process.

People have responsibilities, pressures, history, expertise, and requirements that may not be visible from another part of the organization. And sometimes progress requires a real tradeoff.

Maybe one team gets more time, which means another team has less.

Maybe a deadline stays fixed, so scope has to change.

Maybe one group agrees to absorb extra work this time—but that cannot quietly become the expectation every time.

Those choices need to be visible.

If one team is giving something up so another part of the work can succeed, everyone should understand that decision, why it was made, and whether it is sustainable. Otherwise, a one-time compromise can easily become the new normal—and eventually create another problem.

So I learned to make those needs, tradeoffs, and decisions more explicit.

What does Marketing need from Technology?

What does Finance need before it can approve something?

What does the creative team need to produce strong work?

What does leadership need to decide?

Where do two legitimate requirements conflict?

And where do we need an explicit conversation or negotiation instead of allowing people to discover the conflict halfway through execution?

That human reality became as important to me as the process itself.

When people understand what others need, what tradeoffs are being made, why a decision was made, and how their work connects to the whole, collaboration becomes much more possible.

Seeing the Whole

The value is often in the connections between the pieces.

Over time, I became increasingly interested in the whole environment around the work.

I want to understand enough to see what may be missing, where a dependency is forming, where information is not traveling, where ownership is unclear, or where a decision is going to affect someone who has not yet been part of the conversation.

I also tend to think ahead.

What happens after this decision?

Who will need to know?

What will they need in order to act?

What happens when this reaches another team, market, system, or stakeholder?

That way of thinking has shaped my work from project management into program leadership and, eventually, into enterprise-level integration.

Today, I often find myself helping leadership teams create one connected view of work that otherwise exists across many separate functions, conversations, priorities, and assumptions.

Why I Built Nooqleo

Better execution should make work better.

Nooqleo began with a belief that organizations could execute complex marketing work more effectively with stronger project leadership, operating discipline, and cross-functional coordination.

As the work expanded, so did that belief.

Execution improves when people understand the goal, know how decisions will be made, see how their work connects to others, and have a structure that supports them.

Confusion, duplicated effort, unclear authority, constant escalation, and last-minute changes affect delivery. They also affect the people doing the work.

I believe good operating systems should create clarity, accountability, and momentum while making it easier for capable people to work together.

That philosophy sits at the center of Nooqleo today.

How I Work

Curious about the whole. Practical about what needs to move.

01

Understand First

I want to know what leadership is trying to accomplish, what teams are experiencing, and what the evidence is showing before deciding what should change.

02

Connect the Dots

I naturally look across priorities, decisions, dependencies, people, and functions to understand how one part of the system is affecting another.

03

Make Complexity Usable

The goal is to create enough clarity and structure that people understand what matters, what they own, and what needs to happen next.

04

Make the Work Visible

Many problems become easier to solve once requirements, tradeoffs, decisions, and dependencies are visible enough for people to discuss them honestly.

05

Leave Something Stronger Behind

The work should leave clearer ownership, better operating habits, and a system the organization can continue using.

Perspective

Built across cultures, industries, and ways of working.

My career has been shaped by moving between countries, organizations, functions, and different kinds of work.

That has made adaptability part of how I lead.

I am comfortable entering unfamiliar environments, learning quickly, asking questions, and connecting perspectives that may not naturally sit together.

It is also why I have never been particularly comfortable with the idea that people—or careers—must fit neatly into one box.

Seeing across disciplines, cultures, and ways of working has become one of the most useful perspectives I bring to complex work.

Work With Liliana

Bring senior perspective, structure, and cross-functional leadership into the work.