Process Clarity Must Precede Automation: Manuel Ramírez on Why Process Comes First
- Talent Precision Group
- 3 days ago
- 7 min read
Manuel Ramírez is Vice President of Data Insights and Process Automation at PPHE Hotel Group, where he works at the intersection of finance, automation, and decision enablement.
Having spent more than a decade evolving from FP&A and group reporting into broader transformation leadership, Manuel has seen first-hand how finance functions are being reshaped by data, process redesign, and automation.
In this Precision Perspectives conversation, he shares why the biggest barriers to transformation are rarely technological, why finance must evolve beyond reporting cycles, and why process clarity must precede automation
You started your career in finance and FP&A, and today you lead Data Insights and Process Automation. Looking back, what were the key moments or decisions that pushed you beyond traditional finance into a more data and transformation-focused role?
The shift wasn’t a single leap, it was a series of moments where the job stopped being “finance” and became “decision enablement.” Early in my FP&A career, I enjoyed building models and shaping narratives, but as the organisation grew, the complexity of the data landscape grew even faster. Planning and performance discussions increasingly depended on data coming from many different systems, teams, and operational realities; not just the ledger.
A key decision was to stop treating data as an input to finance and start treating it as a product: governed, standardised, accessible, and designed for decision-making. Once you take that perspective, you naturally move from producing reports to building platforms, from explaining numbers to shaping how the business measures performance.
Another decisive moment was taking accountability for automation. Automation forces clarity: you quickly learn that the bottleneck is rarely technology, it’s process ambiguity and inconsistent ways of working. That pushed me into a broader transformation role: translating between business needs and technical solutions, aligning stakeholders, and creating the conditions where data and automation can scale.
Ultimately, I didn’t “leave” finance. I extended it into data foundations, governance, and scalable transformation.
You mentioned that at a certain point, it became difficult to both manage the
numbers and extract meaningful insights. Was there a specific moment where you realised the traditional FP&A model was no longer sufficient?
Traditional FP&A rhythms can become a trap: you’re constantly reconciling data instead of interpreting it, and you’re answering why the numbers don’t match instead of what the numbers mean. The clearest signal was when leadership discussions started drifting toward operational questions; customer behavior, channel performance, service interactions, demand drivers and the FP&A toolkit alone wasn’t enough.
That’s when the priority shifted to creating a single source of truth and building a scalable decision layer on top of it: consistent definitions, shared metrics, governance, and repeatable analytics. Once you have those foundations, insights become a product, not an ad hoc exercise.
So the “moment” was realising the limiting factor wasn’t analytical ability, it was the system and operating model behind the analysis.
There’s a lot of discussion around finance becoming more data-driven, but in
reality, many teams are still operating in very traditional ways. From your perspective, what is the biggest gap between how finance functions should be operating today and how they actually operate?
The biggest gap is that many finance teams still behave like producers of reports, when they need to become decision-makers.
In practice, finance often remains spreadsheet-centric, exception-heavy, and built around personal routines rather than standardised processes. That creates three problems:
1. Speed — too much time is spent collecting and reconciling, not analysing.
2. Trust — teams lose credibility when definitions vary or numbers don’t align.
3. Scalability — knowledge lives in individuals, not in systems or reusable assets.
In my view it is key that there is a central data and analytics function that takes care of: shared definitions, governed metrics, clear ownership of data, and an analytics layer that enables self-service for routine questions, so finance can focus on what only finance can do: framing trade-offs, guiding investment decisions, challenging assumptions, and shaping strategy.
To get there, you need more than tools. You need a mindset shift: finance is not a monthly cycle; it’s a continuous decision function.
You’ve been ahead of the curve in automation, from RPA through to AI adoption.
What have you learned about the real impact of automation and AI in finance, versus what the market often expects?
The market often expects automation and AI to “replace people.” The reality, when done properly, is that it replaces friction: waiting, rework, reconciliations, manual handoffs, and repetitive decisions.
The most important lesson is that impact comes from process clarity and adoption, not from the sophistication of the technology. RPA can deliver massive value if the process is stable and standardised. AI can deliver massive value if the data is governed and the decision boundaries are clear. Without those foundations, both become expensive experiments.
Another lesson is that you must measure outcomes in business terms: cycle time reduction, error reduction, improved customer experience, capacity released, and decision speed. The credibility of automation programs depends on quantifying value and communicating it transparently.
Finally, AI changes the nature of work. It doesn’t eliminate the need for humans, it shifts humans toward higher judgment work: exception management, risk framing, stakeholder alignment, and continuous improvement. Organisations that succeed treat automation and AI as part of an operating model change, not an IT upgrade.
You highlighted that profiles who can combine finance, process understanding,
and data capability are still very rare. What specifically is missing in most finance professionals today, and what differentiates the few who are able to operate effectively in a data-driven environment?
What’s often missing is not traditional finance skills, it’s process thinking and comfort with change.
Many finance professionals are trained to execute reliably within existing routines. They become excellent at operating inside an exception-based environment, where every special case has a reason and every step has a historical justification. The challenge is that automation and data-driven operations require the opposite: simplification, standardisation, and the ability to say, “Let’s redesign this to work 80/20.”
The few who thrive in a data-driven environment typically share three traits:
• Systems mindset: they think end-to-end across functions, not in departmental silos.
• Curiosity + literacy: they don’t need to be engineers, but they understand how data flows, what “good data” means, and how to ask the right questions.
• Change leadership: they can challenge the status quo without losing stakeholders; they can quantify risk, run controlled changes, and build confidence.
In short, the differentiator is the ability to move from “doing the work” to “designing how the work should be done.”
You mentioned that the biggest challenge is not technology, but changing how
people work. Why do you think finance functions struggle so much with process transformation, even when the technology is already available?
Finance struggles with process transformation because finance is built around risk management and change is often perceived as risk, even when it reduces risk.
In many organisations, processes exist because “that’s how we’ve always done it,” and the rationale has been lost over time. When you ask why a step exists, you often uncover institutional memory rather than true necessity. That makes redesign difficult, because people fear removing a step they don’t fully understand.
Another reason is that finance work is frequently exception-driven. If you design processes around every exception, you never standardise. Transformation requires discipline: define the standard path, isolate exceptions, and continuously reduce the exception set over time.
Finally, transformation needs dedicated roles and time. You need sponsorship, clear ownership, and people who are capable of translating between current reality (“as-is”) and the target design (“to-be”); including what controls, governance, and behavioural changes are required.
Technology is the accelerator. The real work is the human and process redesign.
As automation continues to evolve, you suggested that a large part of
traditional finance work could be automated. How do you see finance roles evolving over the next 3–5 years, and which profiles will still be relevant?
Over the next 3–5 years, finance will split more clearly into two worlds:
Automated execution: routine transactional work, reconciliations, reporting production, and standard controls will become increasingly automated, driven by workflow automation, AI-assisted close, and agent-like capabilities. The expectation will be faster cycles, fewer manual touchpoints, and higher data quality.
Decision leadership and transformation: the roles that remain critical will be the ones that shape decisions and redesign the operating model.
The finance professional of the future is someone who can integrate data, process, controls, and business context into better decisions.
If you could share one “Precision Perspective”, a lesson, insight, or guiding belief
that others could carry into their own careers, what would it be?
Over the years, I’ve seen many situations where people expect systems, automation or AI to magically fix things. But if the process is messy, unclear, or based on habits rather than real needs, you just end up automating confusion. I’ve learned that you need to stop first and ask simple questions: Why do we do this? What happens if we don’t? Who actually uses this output?
Another important thing is not to be afraid of change. In finance especially, people stick to routines because they feel safe, even when they no longer add value. Most of the work we do every day exists because “it has always been done that way,” not because it’s genuinely needed. Challenging that takes effort and sometimes uncomfortable conversations, but that’s where progress happens.
So my main perspective would be: focus on simplifying how you work, be curious, and don’t wait for permission to improve things. The successful professionals I have the opportunity to work with are usually the ones who try to make things better, even if they don’t have all the answers at the beginning.
What becomes clear throughout the conversation is that finance transformation is rarely limited by technology. More often, the real challenge lies in process clarity, operating discipline, and the willingness to rethink long established ways of working.
As finance functions continue to evolve beyond traditional reporting cycles, the expectations placed on finance professionals are evolving too. Technical capability still matters, but increasingly the differentiator is the ability to connect data, process, controls, and business context to support better decisions.
For Manuel, progress starts with simplification. Asking better questions. Challenging unnecessary complexity. Creating systems and processes that allow people to spend less time reconciling information and more time generating meaningful insight.
Ultimately, the future of finance will not be defined by how much work can be automated, but by how effectively organisations redesign the way they operate around it.
Perhaps the clearest lesson from the conversation is that process clarity must precede automation.
Precision Perspectives is an interview series by Talent Precision Group, exploring the experiences, perspectives, and leadership thinking shaping modern finance.
To discuss finance leadership, transformation, or hiring across Europe, contact Talent Precision Group at enquiries@talentprecisiongroup.com or +31 20 323 4665.
Comments