Author: Katarzyna Kwiatowska

16Jun

AI Won’t Take HR Jobs

AI Won't Take HR Jobs | Smart People Blog

AI Won't Take HR Jobs

AI won't take HR jobs. It will take them from HR professionals who understand systems.

Most companies today live under the illusion that artificial intelligence is the biggest revolution. It's not. The real revolution in HR departments happened when advanced HCM systems became the standard – SAP SuccessFactors, Workday, Oracle.

And here's the brutal truth nobody says out loud:

Companies spend millions on technology implementations, then can't use them – because there aren't enough people who combine HR knowledge with technical understanding.

Business keeps making the same mistake: burning through massive budgets by bringing in pure IT departments or developers to configure a simple workflow or update an org structure. Why? Because the internal HR team doesn't understand the tool they're working with – and is afraid to click anything.

The result? Frustration, delays, and a system that weighs you down instead of helping. Modern business needs people – both inside organizations and as external experts – who can manage these tools from an HR process perspective.

And right now, the market is running out of them.

The "human" trap in Human Resources

Most HR professionals learned their craft when the height of HR technology was Excel and a basic payroll system. They learned psychology, relationships, labor law, soft skills management. And that's still enormous value that no machine will replace.

But today, it's simply not enough.

I'm not saying you need to start coding. I'm talking about a basic understanding of the logic behind the system you manage.

  • A recruiter who doesn't understand sourcing automation mechanics will quickly lose ground to someone who can connect the system with search algorithms.
  • An HRBP who can't independently pull and interpret analytical data from the system will stop being a partner to the board. They'll get ready-made recommendations from someone who can read that data.
  • An HR Admin / Specialist who doesn't know the system's logic – who doesn't understand how the platform "reads" org structure – will fall behind someone who has that knowledge cold.

This isn't a five-year outlook. This is the next few months. The market is rapidly polarizing between digital HR professionals and those who stay in the era of paper and Excel.

How to stay in the game

Here's the good news: workflow configuration, employee data structures, process logic – all of this can be learned. Much faster than you think. You don't need a computer science degree – you just need to learn from practitioners who've lived and breathed these systems. AI will help too, because understanding processes is one thing – configuring them is another. And those who know both will use AI to their advantage: streamlining and optimizing HR processes, automating routine tasks, and freeing up time to bring real value to the business – and to secure their own position in it.

Where the demand actually is

The most in-demand and best-paid area in the market right now – both in internal roles and consulting projects – is SAP SuccessFactors. Companies are desperately looking for people who can handle this system from a functional and business perspective.

So instead of fearing that technology will take your job – make it your biggest asset and your ticket to top-tier projects.

At Smart People Global Academy, we're opening a new edition of the SuccessFactors Employee Central Consultant course. This isn't a theoretical lecture. It's an intensive, hands-on program delivered by implementation practitioners – designed to give you the hard, market-rare skills of a functional consultant.

Secure your professional position and step up to the next level of HR.

👉 Program details and registration here: https://smartpeople.com.pl/en/smart-people-global-academy/

Thinking about building functional SuccessFactors skills?

I'm always happy to talk through what that path actually looks like, whether you're coming from HR or from outside it.

Let's Talk
16Jun

The Hidden Cost of a Failed SuccessFactors Implementation – And How to Avoid It

The Hidden Cost of a Failed SuccessFactors Implementation – And How to Avoid It | Smart People Blog

The Hidden Cost of a Failed SuccessFactors Implementation – And How to Avoid It

You knew the price going in. The contract was signed, the budget approved, the implementation partner selected.

You didn't know the total.

The go-live happens. Everyone is exhausted, relieved, cautiously proud. The partner hands over the documentation and moves on to their next engagement. And then, slowly, quietly – the system starts to drift. Adoption stays low. Workarounds multiply. Configuration decisions that made sense during the project now make no sense at all, and nobody left in the building can explain them.

This is not a dramatic failure. There is no single moment it breaks. That is exactly what makes it so expensive.

What's actually on the bill

I know of one organization – mid-sized, serious investment, everything done by the book – where, eight months after go-live, compensation review data was still being cross-checked against a manually maintained spreadsheet. The reason: no one could trace why a specific workflow had been configured the way it was. The implementation partner was long gone. The person who made the original configuration decision had left the company. The HR team spent weeks working around a live production system they were, theoretically, in charge of.

That is not an extreme case. That is a Tuesday.

When companies think about implementation risk, they think about the invoice. That is the number they negotiated, approved, and paid. It is not the total.

Rework. Re-configuring a live system costs significantly more than getting the configuration right the first time. Every process built incorrectly has to be unwound, corrected, and retested – while the business is still running on top of it.

Workaround maintenance. The parallel spreadsheets, the manual processes, the unofficial systems that fill the gaps – they do not go away after go-live. Someone maintains them. That someone's job was supposed to be running the actual platform.

Partner dependency. Every question that goes back to the implementation partner after handover costs. Time, money, and increasingly, leverage. You are calling someone whose engagement officially ended. They know it. You know it.

Deferred ROI. A system running at 40% of its capability is still a system paying full licensing costs. That gap does not appear on any invoice. It compounds every quarter.

Credibility erosion. The HR team that owned this implementation becomes, in leadership's eyes, the team that delivered a complicated system nobody fully uses. Rebuilding that trust takes longer than the original project did.

Talent loss. The people managing a troubled implementation often leave. Project fatigue, impossible expectations, being the internal face of something that is not working – it burns through capable professionals.

None of these were on the original invoice. All of them were on the bill.

Why it keeps happening

The pattern is consistent. The client arrives at an implementation with full budget for the platform and the partner – and almost nothing invested in their own readiness. Processes have not been mapped. The project owner was assigned based on availability, not qualification. The internal team is learning and deciding simultaneously, in configuration workshops, under deadline.

Implementation partners are scoped to delivery. They are not there – and should not be expected – to build your organization's long-term capability to own the system. The moment their engagement closes, that responsibility transfers. What does not transfer is the knowledge.

The most expensive moment in an SAP SuccessFactors implementation is when the partner's engagement ends and your team realizes they cannot answer a question without picking up the phone to call them.

What preparation actually looks like

Map your processes before you open a configuration workbook. SuccessFactors can model complex organizational structures and HR workflows with precision. But it cannot model what you have not defined. Organizations that enter an implementation with documented processes – even imperfect ones – move faster, make better decisions, and end up with configurations they can explain and maintain.

Build internal literacy before the partner arrives. Your project owner, your system administrator, the HR team members who will run this platform after go-live – they need to understand SuccessFactors before they are sitting in configuration workshops trying to learn and decide at the same time. Two different cognitive tasks. Doing them simultaneously is where mistakes get locked into production.

Build a knowledge foundation your team can use independently. Post go-live, questions do not stop. What changes is who is available to answer them. Teams that have structured resources and documented decisions dramatically reduce the dependency that generates those post-handover support calls.

The item nobody orders

There is one item that prevents most of what is listed above. It is also the one most organizations never order: an independent advisory voice – someone whose job is not to close the project but to make sure the outcome holds. Someone who tells you the inconvenient truths about process gaps and configuration decisions before they become line items on a bill you weren't expecting.

It is, by far, the least expensive thing on the table.

Build the foundation first

Most organizations approaching a SuccessFactors implementation do not need more information about the software. They need operational clarity before the configuration starts.

That is what we built the Smart Knowledge Hub for.

Planning an implementation, or already living with one that's drifting?

I'm always happy to compare notes on what readiness actually looks like before configuration starts.

Let's Talk
15Jun

You Don’t Need 5 Years in HR to Start a Career in HR Tech

You Don't Need 5 Years in HR to Start a Career in HR Tech | Smart People Blog

You Don't Need 5 Years in HR to Start a Career in HR Tech

I hear this regularly from people who want to move into SuccessFactors consulting: "I don't have an HR background. Would that be a problem?" My honest answer: probably not in the way you think. Let me explain why – and what the actual barrier looks like.

The Assumption

The logic seems obvious on the surface. SAP SuccessFactors is an HR platform. HR platform → HR experience required. Clean equation.

But this collapses the moment you look at what the job actually involves.

A SuccessFactors consultant doesn't run performance cycles. They don't manage employee files, write HR policies, or handle recruitment pipelines. What they do is understand how those processes work – and then configure a complex system to support them, solve problems when it breaks, and translate between the people who know the business and the people who know the software.

That's a systems-and-process skill. It's analytical, logical, and heavily communication-driven. It rewards people who ask good questions, think in structured ways, and don't flinch at complexity.

This doesn't live exclusively in people with HR careers.

Who Actually Thrives in This Work

Over the years, I've worked with excellent consultants who came from project management, business analysis, payroll, IT, and finance operations – people who had never spent a day inside an HR department. They built strong careers because the underlying skills transferred cleanly and they learned the platform properly.

I've also seen HR professionals with a decade of experience struggle, because they'd never had to think in systems or translate business requirements into technical configuration.

Background is context. It's useful. It's not the job.

Profiles that succeed

Project managers, business analysts, payroll specialists, IT professionals, finance and operations people, and career pivoters with strong analytical foundations.

What the Real Gap Looks Like

Here's where things get specific – and honest.

The reason many people who could do this work don't get the chance isn't their CV. It's the platform itself.

SAP SuccessFactors has real depth. It's modular, it's configurable, and clients pay good money to work with people who know it – not people learning on their project. The credential that signals competence in this industry is SAP certification. It's what opens the door.

The gap is almost never "I don't have enough HR experience." The gap is "I don't know the platform well enough yet." That's a different problem – and it's a solvable one.

The Path Is Shorter Than You Think

The people who break into this successfully share a pattern: they stop waiting for experience to arrive organically and go learn the system deliberately. Structured preparation, real access to the platform, proper exam preparation – and then the certification that tells every employer and client that the knowledge is real.

At Smart People Global Academy, we built our Employee Central course specifically for this: people who are ready to move seriously into SuccessFactors consulting and need the preparation to get there.

  • SAP certifies – we prepare you to pass, and more than that, to actually work
  • Real system access throughout the course
  • Instructors who have delivered actual SuccessFactors implementations
  • Structured content built around what the role demands, not just the exam

If you have an analytical mind, you work well under pressure, and you're not afraid of complex systems – the five-year HR career is not the prerequisite you think it is.

The platform knowledge is. And that's exactly what we're here for.

Ready to move into SuccessFactors consulting?

Explore the Smart People Global Academy Employee Central course – built for people who are serious about making the transition.

Explore the Course

Questions? Write to Kasia directly:
katarzyna.kwiatkowska@smartpeople.com.pl

15Jun

What Makes a Great SAP SuccessFactors Trainer – And Why It Matters More Than the Syllabus

What Makes a Great SAP SuccessFactors Trainer – And Why It Matters More Than the Syllabus | Smart People Blog

What Makes a Great SAP SuccessFactors Trainer – And Why It Matters More Than the Syllabus

Katarzyna (Kasia) Kwiatkowska  |  May 4, 2026

I want to say something most training providers will not say out loud: a well-designed curriculum delivered by the wrong person is not just ineffective. It is actively misleading. Participants finish the course believing they are prepared. They are not. And nobody finds that out until the project is already in trouble.

SAP SuccessFactors training has a structural weakness that sits just beneath the surface of most programs. The content is usually adequate. The certification paths are documented. The syllabi are thorough. But the question almost nobody asks before enrolling – who is actually teaching this, and when did they last work on a live implementation – is the one question that determines whether the training is worth anything at all.

I have sat through a lot of training in my career. Some of it was genuinely useful. Some of it was a well-organized tour of slides that had nothing to do with the work waiting for me on Monday morning. The difference was never the syllabus. The difference was always the person delivering it – and more specifically, whether that person had ever carried real responsibility inside a live system, with a client watching, when the go-live date was not moving.

What happens when they have not

A participant asks a question that falls slightly outside the prepared material – a configuration edge case, a conflict between modules, a scenario that only surfaces in real projects. A trainer without operational depth returns to the slide. They give a technically accurate response that does not address what was actually being asked. The participant writes it down anyway, because there is no way to know, in that moment, that the answer is incomplete. They find out later. Usually in front of a client.

Practitioners vs. theorists

Certification candidates who train with practitioners versus theorists do not just perform differently on exams. They perform differently on projects. A consultant who learned SuccessFactors from documentation can navigate the system under expected conditions. A consultant who learned it from someone who has been inside a failed implementation, a rushed migration, a module rollout that uncovered three years of dirty data, knows how to navigate it when conditions are not expected. That is the consultant clients remember.

The practitioner-theorist distinction sounds obvious when you say it out loud. It is apparently not obvious enough, because the majority of SAP SuccessFactors training programs do not make it central to how they select instructors. They select on certification, on availability, on cost. Knowing how to pass a certification and knowing how to prepare someone else to do real work in a real organization are entirely different competencies, and confusing them is how you produce consultants who look qualified on paper and underperform on the ground.

Connecting technical content to organizational reality

The second dimension where training programs most consistently fail is connecting technical content to organizational reality. A compensation cycle is not just a configuration exercise. It involves HR, finance, legal, and often the executive layer. An Employee Central implementation is not just a data migration – it is an organizational decision about how people, roles, and structures will be represented in a system that downstream processes depend on. A trainer who teaches module mechanics without teaching the organizational weight those mechanics carry is preparing people for an exam. Not for a project. The gap between those two is where expensive mistakes live.

The third dimension: teaching to the person

There is a third thing I look for in a trainer, harder to name: the difference between teaching to the material and teaching to the person in front of you. The best trainers slow down precisely when a topic feels simple, because that is usually where the real misunderstandings hide. They ask questions that expose understanding rather than reward participation. They tell stories about the mistakes they made early in their careers, because those stories do more work than any slide. They are invested in whether the knowledge has actually landed – not whether the session ran on time.

How we think about this at Smart People Global Academy

This is what we think about when building training at Smart People Global Academy. Our trainers are practitioners who are still active in implementations. They teach SuccessFactors because they work in it, not because they retired from it. The system changes, client environments change, and the scenarios surfacing in real projects right now are not the same ones from three years ago. A trainer teaching from a 2021 memory is not the same as a trainer teaching from last quarter's project. Participants deserve better than that.

What training providers won't tell you

Most training providers market their programs on content – hours, module coverage, pass rates. These are not meaningless. But they are not the thing that determines whether someone walks out ready to do the work.

SAP issues the certification. What determines whether someone deserves it – and what they can actually do with it – is the person who prepared them to earn it. Before enrolling in any SAP SuccessFactors training program, ask who is teaching it. Ask when they last delivered a live project. The answers will tell you more than the syllabus ever will.

Train with practitioners who are still in the field

Smart People Global Academy courses are delivered by consultants active in live implementations. Explore our SAP SuccessFactors preparation programs.

Explore the Academy

Questions about our training programs? Write to Kasia directly:
katarzyna.kwiatkowska@smartpeople.com.pl

28May

I Don’t Pick Up the Phone for Recruiters Anymore

I Don't Pick Up the Phone for Recruiters Anymore | Smart People Blog

I Don't Pick Up the Phone for Recruiters Anymore

By Katarzyna (Kasia) Kwiatkowska | CEO, Smart People

If you've been in the HCM ecosystem long enough, you've heard this — at conferences, in conversations with other consultants, in LinkedIn comments. Experienced professionals with certifications and real implementations under their belt — they've had enough.

Enough of recruiters offering "some SAP thing" without knowing if it's SuccessFactors or S/4HANA. Enough of 40-minute calls that end with the discovery they're looking for someone completely different. Enough of sharing your rate only to watch it circulate across the market without your control.

But there's something worse than bad offers. It's the moment when your current project ends in three months — and you have to start looking. You update your LinkedIn status. You write posts. You send messages. Suddenly the whole market knows you're looking. Your client might find out too. And instead of calmly finishing the job — you're stressing about what comes next.

That's exactly why we built something to solve this problem.

Why HCM Consultants Hate Looking for Projects

Not because they're lazy. Because the process is embarrassing.

You get LinkedIn messages from recruiters who can't tell Employee Central from SAP Basis. You waste time on phone calls only to learn after 40 minutes that they need someone completely different. You share your rate — and you have no idea where it ends up or who sees it.

Or you reply to a "Senior SAP Consultant — exciting global project!" post, and it turns out to be a support role at half your rate, full-time, on-site somewhere you don't want to go. Sound familiar? Most consultants we talk to know this all too well.

Looking for a Project Shouldn't Be a Project in Itself

At Smart People, we have a network of SAP SuccessFactors, Workday and Oracle HCM consultants from across Europe and beyond. We built something we needed ourselves — because we've been training, advising and connecting people with projects in this ecosystem for years.

It's called the Smart People Consultant Network, and here's how it works:

How the network works

You register once. You enter your modules, certifications, payroll experience by country, preferences (remote, hybrid, on-site), and availability. 5 minutes.

Your data is yours. We don't publish your profile anywhere. We don't share your rate with anyone without your consent. Clients see an anonymised competency card — no name, no rate. Only when both sides want to talk do we arrange a meeting.

When a project comes up for you — we reach out. You decide whether you're interested. No spam with offers that have nothing to do with your profile.

Nobody has to know you're looking. Your current client won't see your profile on any portal. You don't have to change your LinkedIn status to "open to work". You're in our network — and when the right moment comes, we reach out.

This Is Not a Job Board

We match people to projects by hand.

We don't have a "Browse 5000 consultants" tab. We don't collect CVs for stockpiling. We don't send mass emails with offers.

Every consultant in our network is either known to us personally or verified through real projects. A consultant with EC certification and DACH payroll experience is not the same as a consultant with EC certification who's only done core HR in one country. A recruitment agency can't see that difference. We can — because we've been operating in this space for years and we know it inside out.

Where Are the Projects

Europe from Scandinavia to the Balkans — Germany, Austria, Switzerland, Benelux, UK, Poland, Czech Republic, Romania, Hungary. A growing number of projects in the US, Brazil, India, UAE and Australia.

Remote, hybrid, on-site — it depends on the project. But you always know upfront, before you decide.

5 Minutes Now, Peace of Mind for Months Ahead

Registration doesn't commit you to anything. You don't sign a contract. You don't pay commission. You leave your profile — and we do the rest.

Next time your project is coming to an end, you won't have to look for anything. Because the right project will find you.

Let's Talk

Join the Smart People Consultant Network — register in 5 minutes and let the right project come to you.

Or reach out directly with any questions. It's a conversation, not a pitch.

Join the Network
28May

What HR Leaders Get Wrong About Upskilling Their Teams on SuccessFactors

What HR Leaders Get Wrong About Upskilling Their Teams on SuccessFactors | Smart People Blog

What HR Leaders Get Wrong About Upskilling Their Teams on SuccessFactors

By Katarzyna (Kasia) Kwiatkowska | CEO, Smart People

Every few months, I speak with an HR leader who is frustrated.

The SuccessFactors implementation went live. The vendor delivered training. People attended. And yet — six months later, the system is being used at a fraction of its potential, workarounds are spreading, and the HR team is quietly going back to Excel.

The technology isn't the problem. The way organizations think about upskilling their people around the technology — that's where things go wrong.

After years of advising organizations on SAP SuccessFactors implementations and building competency frameworks around HR tech, I've come to recognize a pattern. Here are the most common mistakes I see — and what to do instead.

Mistake #1: Treating Training as a One-Time Event

Implementation projects have timelines. Training gets scheduled into that timeline — usually in the final sprint before go-live, when everyone is already exhausted and overwhelmed.

People sit through hours of system walkthroughs. They nod. They pass the sign-off checklist. And then they return to their desks and can't remember half of what they learned, because they have no immediate context to anchor it to.

Learning doesn't work that way. Competence is built through repetition, application, and reinforcement over time — not through a single dense session squeezed between data migration and UAT.

The organizations that see lasting adoption treat training as an ongoing process, not a project deliverable. They build internal knowledge infrastructure. They invest in people who can continue developing the team after the implementation partner has left.

Mistake #2: Training the Wrong People

There's a version of "we trained our team" that means: we trained two super users, who were then expected to cascade knowledge across the entire HR department.

Super users are not a substitute for broad competency.

When only a handful of people truly understand the system, you create bottlenecks. You create dependency. And when those people leave — and they do leave, often precisely because their market value has just increased — the institutional knowledge walks out the door with them.

Effective upskilling means building a wider base. Not everyone needs to be an expert, but everyone who touches the system needs to understand it well enough to use it confidently, escalate intelligently, and recognize when something isn't working as it should.

Mistake #3: Separating HR Knowledge from System Knowledge

This is perhaps the subtlest mistake, and the most damaging.

SuccessFactors is not a neutral tool. It has logic embedded in it — about how organizations structure compensation, how performance processes flow, how talent data connects across modules. To configure it well, to use it well, to troubleshoot it well — you need to understand both the system and the HR domain it operates in.

The gap that costs the most

I've seen teams who are technically proficient in navigating the interface but have no idea why a particular workflow is set up the way it is. They can click the buttons. They can't question whether the buttons are leading them anywhere useful.

The gap between "knowing the system" and "understanding what the system is supposed to do for your organization" is where most SuccessFactors frustration lives.

Mistake #4: Waiting Until Something Breaks

Reactive learning — training people after a problem has already surfaced — is expensive. It's expensive in time, in morale, and often in data quality that has to be manually corrected.

Proactive capability building means identifying the knowledge gaps before they create operational problems. It means building your team's understanding of upcoming modules or configuration changes before they're rolled out. It means having a place your HR team can go to deepen their skills on their own schedule, without waiting for a formal implementation project to justify it.

What Actually Works

The organizations I've seen handle this well have a few things in common.

The pattern behind lasting SuccessFactors adoption

They think about their HR team's SuccessFactors competency as an asset — something to be built deliberately and maintained over time, the same way they think about the system itself.

They invest in quality training that connects process logic to system functionality — not just screen-by-screen navigation.

And they create the conditions for continuous learning: internal knowledge sharing, access to good external resources, and people who are genuinely skilled at transferring that knowledge.

The system is only as effective as the people using it. That's not a limitation — it's an opportunity, if you treat it like one.

Let's Talk

If you want a good foundation — the Smart Knowledge Hub has the materials. Quality resources, real depth, built for HR professionals who take this seriously.

If your team needs more than resources, the Smart People Global Academy is the next step — structured training, taught by practitioners who know both the system and the HR domain.

Or reach out directly. It's a conversation, not a pitch.

Write to Me
22Apr

What SuccessFactors Decision-makers Read Over the Weekend — And Why It Didn’t Surprise Me

What SuccessFactors Decision-Makers Read Over the Weekend | Smart People Blog

On Thursday we launched the Smart Knowledge Hub. I didn't write anything about it over the weekend — I wanted to see what people were actually reading before I started commenting on it.

Today, Monday morning, I know a little more.

The most-opened resources aren't for those just starting their SuccessFactors journey.

They're for decision-makers in the middle of an implementation.

The partner selection framework, the questions to ask before signing a contract, the go-live readiness checklist. The e-book — the one with 27 chapters walking you step by step through the entire implementation path — is also getting significant attention.

And that doesn't surprise me.

SuccessFactors Is One of the Most Complex HCM Systems on the Market

When a company implements SF for the first time, it walks into a world it had no way of learning beforehand. Modules that connect to each other in non-obvious ways. Architectural decisions whose consequences you only see two years later. Quarterly SAP releases that can change how entire processes work. Integrations with payroll, ERP, time tracking systems — each with its own logic and limitations.

A good implementation partner knows all this. They have their methodology, experience from previous projects, their own best practices. But — and this is natural, not a criticism — they look at your project through the lens of their own craft. Their own schedule. Their own consultants who happen to be available.

You look through a completely different lens. Through your business. Your processes. Your regulations. Your people who'll work with this system for the next ten years.

For these two perspectives to balance each other out, you need expertise on the client side. Someone who understands SF deeply enough to ask the right questions, evaluate proposals, recognize trade-offs — and do it in real time, during the workshop, not three weeks later when the decision is already in the project documents.

The Gap Most Companies Don't See

Most companies simply don't have this expertise. Because they're implementing SF for the first time. Because their internal HR IT team has eight other priorities. Because building that kind of competence takes years, and the project needs to happen now.

Embedded Advisor — A Model That Works for Both Sides

For situations like this, at Smart People we offer the Embedded Advisor service. Our senior consultant joins your team for 2–4 days a week, for the entire duration of the project. Not instead of the implementation partner. Alongside.

What they do:

  • Prepare you for every workshop — explaining what the implementation consultant will propose and why, so you walk into the room prepared
  • Flag risks in real time — "this solution will work now, but in two years it will block you from expanding into X"
  • Translate architectural decisions into business language
  • Build your team's competence alongside every conversation, so after go-live the system is yours, not the partner's

A Model That Works for Three Sides

The client gets an equal footing in conversations with the implementation partner. The implementation partner gets a better-prepared client, which in the long run means a better project and fewer escalations. The project gets better architecture, because decisions are made with a fuller understanding of business context.

I see this regularly — projects with an Embedded Advisor on the client side end better. Not because implementation partners work worse without us. Because the client knows better what they need.

The Hub Is the First Step

The materials in the Smart Knowledge Hub — the partner selection framework, 20 questions before the contract, the go-live checklist, the e-book about the whole implementation process — are exactly what they are. A first step. They give you knowledge, but not the context of your specific project.

Knowledge In Your Project

The Embedded Advisor gives you knowledge in your project. In your workshops. At your table.

If you've started reading the Hub and are thinking "this is exactly what I'm missing, but in my own company" — write to me. Either directly, or through the form on the page. It's a conversation, not a pitch.

The Hub has been live since Thursday. In a week, I'll know more. In a month — even more. If there are things that should be there but aren't — tell me. We're building this with the market, not apart from it.

Let's Talk

Visit the Smart Knowledge Hub or reach out directly.

It's a conversation, not a pitch.

Write to Me

Get in Touch

Katarzyna (Kasia) Kwiatkowska
CEO, Smart People
Email: katarzyna.kwiatkowska@smartpeople.com.pl
Hub: smartpeople.com.pl/en/smart-knowledge-hub/

30Mar

We Invested in the System. We Forgot to Invest in People.

We Invested in the System. We Forgot to Invest in the People. | Katarzyna Kwiatkowska

We Invested in the System.
We Forgot to Invest in the People.

Katarzyna Kwiatkowska  |  CEO, Smart People

Every year, companies spend significant budgets on HR technology. Platforms get implemented. Suppliers and contracts get signed. Go-live dates get celebrated.

And then, quietly, the same pattern repeats itself.

Adoption slows. Workarounds multiply. Someone is running parallel Excel sheets "just in case." The system that was supposed to transform HR is being used at maybe 40% of its capability — and nobody in leadership knows exactly why, because nobody is asking the right question.

The right question isn't: did we implement correctly?
It's: do the people responsible for running this system actually understand it?

The Gap

I've seen this from both sides — as a consultant and as someone who builds teams. There is a consistent, predictable pattern in HR implementations that fail to deliver on their promise. It's not the technology. The technology works. It's the fact that the humans managing it were never properly equipped to work with it.

This isn't about negligence. It's about a structural blind spot.

When a company invests in a platform like SAP SuccessFactors, the budget goes toward licenses, implementation partners, project management. What rarely makes it into the budget — or the strategic conversation — is the question of whether the internal HR team has the actual competency to own the system once the partner leaves. The other question is: do we manage somehow the change within the organization?

Implementation partners are there to deploy. They are not there to build long-term internal capability. The moment the project closes, your team is on their own — with some support from the implementation partner, but limited. And most of the time, the internal teams are not ready.

Skill Gap Hidden

Here's what makes this problem particularly hard to catch: the people running your HR system often don't know what they don't know.

They can complete the tasks they've been trained to complete. They follow the workflows. They process the data. But when something breaks, when a new module needs to be configured, when a process needs to evolve — they hit a wall. And instead of escalating it as a competency problem, they work around it. Because nobody wants to be the person who admits they don't fully understand the system their company just paid a significant amount to implement.

Leaders, meanwhile, see the dashboard. The data is there. Reports run. Everything looks functional. So there's no signal that something is quietly wrong.

Until there is — usually in the form of a project that stalls, a compliance issue, or a decision made on incomplete information nobody realized was incomplete.

Understanding is not the same as knowledge. But knowledge and competences prove understanding.

Building Knowledge

I want to be direct about something.

I'm talking about building deep knowledge and competences within the organization during the project. What matters is ensuring your HR team has the practical skills to truly understand and manage the system long-term — not just operate it superficially.

That's a different thing entirely.

Building knowledge through hands-on experience and structured training provides the clarity that matters — in project decisions, system governance, and everyday operations that shape outcomes.

What We Do — and What We Don't Claim

At Smart People Global Academy, we prepare professionals for SAP SuccessFactors certification. We design programs around real project practice, not dry theory. We teach the way the system actually behaves on implementations — because Smart People places SF consultants on global projects, and we know firsthand what the gap looks like between someone who understands the system and someone who merely operates it.

We are not the ones who certify. SAP certifies. That's their process, their standard, their badge.

What we do is make sure that when you or your team member walks into that exam — and into every project after it — they are genuinely ready. Not just to pass. To perform.

Because the goal was never the certificate. The goal was the competency the certificate proves.

Is Your Team Really Ready?

If your team is running SAP SuccessFactors and you're not sure how deep that knowledge actually goes — that question is worth asking before the next project, not after.

Let's Talk

09Mar

SAP SuccessFactors Implementation

Implementing SAP SuccessFactors? Your Partner Knows Everything. You Know Almost Nothing.

Implementing SAP SuccessFactors? Your Partner Knows Everything. You Know Almost Nothing. And That's a Problem.

Let me be direct: most companies implementing SAP SuccessFactors are alone during the process.

Yes — they have an implementation partner. They have a project manager. They have a schedule, workshops, weekly status calls. On paper, everything looks professional.

But in practice, there is one fundamental problem.

The implementation partner knows how the system works. The client knows how their company works. And between these two worlds is a gap — through which, every week, decisions fall that the client doesn't fully understand the consequences of.

Not because the partner is dishonest. But because the client has no one on their side who understands SuccessFactors well enough to ask: "Is this really the best option? Or just the fastest one?"

The Asymmetry Nobody Talks About

Every implementation project has an imbalance of knowledge. The partner has delivered many SF projects and knows where the typical traps are. The client is doing one implementation — probably their only one in the next decade.

  • The partner knows which configuration decisions will hurt six months down the line. The client finds out six months down the line.
  • The partner knows that certain workarounds technically work — but create technical debt. The client only sees that "it works."
  • The partner knows how much changes cost after go-live. The client finds out when they receive the change request quote.

This isn't a bad partner. It's simply a situation where one side has significantly more context than the other. And in that situation, even an honest partner — consciously or not — runs the project in a way that's convenient for them, not necessarily optimal for the client.

What's Missing on the Client Side

What's missing is someone who:

  • Understands SAP SuccessFactors well enough to evaluate the partner's proposals — not at the level of "that sounds good," but at the level of "what are the consequences of this approach in six months."
  • Can translate technical language into business decisions — because a Head of HR shouldn't need to understand the difference between an MDF Object and a Foundation Object in order to make a good call.
  • Plays exclusively on the client's team — with no interest in the project running longer, in adding modules, or in avoiding difficult conversations with the partner.

This is what we do at Smart People. We call it Client-Side Advisory — and in practice, it means we bring SuccessFactors expertise to the client's side of the table, not the vendor's.

Three Ways This Works in Practice

There's no single model, because no two projects are the same. But after many conversations with clients, three variants have emerged that cover most situations.

SmartScope — Before You Sign with a Partner

This is the moment where one well-informed voice can save a company from costly mistakes. A few days of focused work before the client enters any contractual commitment. We help structure the project scope, prepare the RFP, and evaluate vendor proposals.

The goal isn't to pick the cheapest offer. It's to understand what's a realistic scope versus a marketing promise. Where are the decisions that will cost double if not clarified now. Which questions are worth asking the partner before everyone signs on the dotted line.

One mistake caught at this stage can save many times the cost of our work.

SmartGuard — A Conscience for the Project in Progress

This model solves the most common problem: the client has an implementation underway, but no one looking at the project through their eyes.

A few days per month throughout the project. We join key meetings. We review configuration decisions. We translate — in the client's language, not in technical jargon — what the partner is actually proposing and what the consequences will be.

Monthly: a short summary of what's going well, what needs attention, what might blow up after go-live.

We're not auditing the partner. We're accelerating the project — because a client who understands what's happening makes decisions faster. And a partner talking to someone who knows SuccessFactors doesn't have to waste time explaining the basics.

A good implementation partner values having someone competent on the other side. A poor partner will be unhappy about it — and that reaction alone tells the client something important.

SmartSide — Our Person on Your Team

For larger projects or clients who want full presence: a dedicated SF consultant who joins the client's team for the duration of the project.

Working 2–4 days per week. Sitting at the same table as the implementation partner — but representing the client's interests only. Preparing the client's team for workshops, flagging risks in real time, helping make decisions as they happen.

And doing something no implementation partner will do: building the internal team's competence. Because after go-live, the partner leaves. The client stays with the system they need to run.

What We're Not

  • We're not an implementation firm. We don't sell our own project. We have no interest in the implementation running longer, costing more, or covering more modules than necessary.
  • We're not an auditor who arrives after the fact to say "you should have done it differently."
  • We're not competition for the implementation partner. Quite the opposite — in the best projects I've seen, both sides of the table had people who understood the system. Decisions were made faster. The project moved smoother. No one wasted time explaining the obvious.

We are on the client's side. That is our only role and our only interest.

Planning an SF Implementation?

If you're planning an SF implementation — or you're already in one and feel like you're getting lost in the technical language — reach out. Even a short conversation can clarify whether you need someone in your corner.

Let's Talk

08Feb

Why I’m Glad We’re Not Poland’s Largest SAP Training Company

Why I'm Glad We're Not Poland's Largest SAP Training Company | Smart People Blog

Why I'm Glad We're Not Poland's Largest SAP Training Company

We could be three times bigger. We consciously choose not to be.

This isn't false modesty or an excuse. We have options. We could record courses once and sell them indefinitely. We could pack hundreds of people into webinars. We could sell platform access and wish people luck.

We don't do any of that.

And this decision – this deliberate "no" – is the smartest thing we've ever done.

Not All Growth Is Good Growth

The business world is obsessed with scale. Higher revenue. More clients. Faster expansion. It's the default success metric, the number that impresses on LinkedIn.

But here's what they won't tell you: scale and quality rarely go hand in hand.

When you're teaching SAP SuccessFactors, you're not selling widgets. You're not moving boxes. You're transferring complex knowledge that will determine whether someone can actually do their job when they return to the office on Monday.

That requires something scale can't provide: attention.

What "Boutique" Really Means

When people hear "boutique," they sometimes think "small" or "amateurish." That's not what I mean.

Boutique means control. It means we know every trainer personally. It means I know exactly what's happening in every course because I'm involved. It means when a participant emails with a question three months after certification, they don't hit a ticketing system – they get a real answer from someone who remembers them.

Boutique Means Relationships, Not Transactions

Our clients don't come to us once. They return. They send colleagues. They call when they're stuck on an implementation six months later. That doesn't work when you're optimizing for volume.

Boutique means a reputation you can stake your name on. When someone asks "Where should I do SAP training?" and your graduates say "Smart People – without hesitation," that's worth more than any advertising budget.

You can't buy that. You can only build it. Slowly. Carefully. With every single interaction.

The Pressure to Grow Kills What Makes You Valuable

I've watched it happen to others. A training company starts brilliantly – passionate trainers, engaged participants, real results. Then they get popular. Demand grows. The owners want to capitalize.

So they:

  • Hire less experienced trainers (cheaper, more available)
  • Increase class sizes (more revenue per session)
  • Standardize content (easier to deliver at scale)
  • Cut "non-essential" support (like post-course Q&A)

And suddenly, what made them great disappears. Participants notice. Reviews drop. Word of mouth shifts from "you have to go there" to "it's okay, I guess."

The business is bigger. But it's worse.

Growth Ate the Value Proposition

I've seen this movie. I'm not interested in the sequel.

"No" as Strategy

Here's what we say no to:

No to the "Buy Access and Good Luck" Model

There's a popular alternative: SAP Learning Hub. Self-study platform. You buy access, get e-books, PDFs, general simulations. And... the rest is up to you.

The Result?

40% of candidates fail the exam on their first attempt. They lose €500, time, and career momentum.

Why? Because reading an 800-page PDF about MDF (Metadata Framework) is like describing color to someone who's never seen it. Without practice, without the ability to ask questions, without someone showing you "aha, so THAT'S where you clicked and why the field isn't visible."

We run 25 live sessions with a 9x certified expert (Flávio Tavares). Monday, Wednesday, Friday, 7:00-9:00 PM CET. Participants can ask questions when stuck. They can watch the trainer configure the system live. They can make mistakes with us, not with a client who'll send a corrective invoice.

No to Lack of Practice

Theory without practice is like describing color to someone who's never seen it. Our participants practice on real SAP instances – the same ones our consultants use on actual client projects. You click, you break, you fix – until you understand. Not screenshots. A live system.

No to Leaving People Alone After the Course

Completing the course isn't the end – it's the beginning. That's why we offer:

  • Bonus webinar with career expert (Sławomir Janczewski, 28 years B2B experience): "How to build your market value and negotiate rates as an SF consultant"
  • Preparation for the official SAP certification exam – practice simulations and test-taking strategy
  • Consultant community support – networking, job search assistance
  • Lifetime access to recordings of all 25 sessions

Our Philosophy

We don't want you to be "just another graduate with a certificate." We want you to be a specialist who knows how to sell your skills and pass the SAP exam on the first try.

It's a choice: easy revenue or real results. We choose results. Every time.

Why This Matters to You

You might think: "Okay, Kasia, but I don't run a training company."

Fair enough. But ask yourself: Where in your business are you being pressured to scale at the expense of quality?

Maybe it's:

  • Taking on more clients than you can properly serve
  • Hiring faster than you can effectively onboard people
  • Expanding into new markets before mastering your core
  • Automating processes that actually need human touch
  • Saying yes to projects that don't fit your strengths

The "growth at all costs" narrative is everywhere. It's tempting. It looks like success.

But sometimes the most strategic move is staying focused. Protecting what makes you excellent. Building deep instead of wide.

Our Version of Success

We're not Poland's largest SAP training company. And we're okay with that.

We're the one people come back to. The one they recommend to colleagues. Where trainers actually want to teach because they have the conditions to do it well.

And that's enough for us.

So I'm Asking You

Where in your business have you chosen focus over scale?

I'd genuinely love to hear your story. Reply or leave a comment – let's talk about what happens when you choose quality over quantity.

Because I think more businesses need the courage to stay boutique.

Ready to Transform Your SAP SuccessFactors Career?

Join our next Employee Central course – 25 live sessions with 9x certified expert Flávio Tavares.

Practice on real SAP instances. Get career coaching. Pass your certification on the first try.

Learn More About Our Courses

Questions? Let's Talk

Kasia Kwiatkowska
CEO & Founder, Smart People Global Academy
Email: katarzyna.kwiatkowska@smartpeople.com.pl
LinkedIn: Connect on LinkedIn

1 2 3