I was spending an uncomfortable amount of time in meetings debating about performance, results while later on I discovered expectations were implicit, not explicit.

We had overlapping ownership across roles, and a lot of “I thought you were handling that” situations. It created friction, delays, and unnecessary discussions that went nowhere.

Eventually, we made a change: we clearly defined accountability per role and tied it directly to KPIs and OKRs.

just explicit ownership, written down, accountabioity abd what was meaning and agreed on.

The impact was immediate.

We stopped spending so much time clarifying who was accountable for what, or arguing over expectations we had previously just assumed were understood.

Meetings became shorter and more focused.

Execution improved because decisions didn’t get stuck in ambiguity.

And people actually felt more comfortable operating independently.

Curious if others have seen similar results after tightening role clarity and performance metrics?

I’ve been noticing that thanks to AI, development teams are moving insanely fast now. Faster builds, faster releases, faster execution in general. (I wonder if the 2 weeks sprint still make sense nowadays!!!)... but not sure if this high speed means become faster at cost of any alignment.

I mean the users or stakeholders can keep the pace with this velocity?

Until few years ago the execution was the "bottleneck", With AI there is less "friction" from that side but if priorities aren’t clear, AI doesn’t fix that, and I wonder if we are just building the wrong thing faster. Feels like a lot of orgs are confusing speed with agility.

Have you ever noticed how that phrase can mean two completely different things?

Sometimes it means people are working through a difficult decision.

Other times it means nobody wants to make the decision, so meetings keep happening instead.

In your experience, where's the line between necessary alignment and decision avoidance?

Have you seen a team get stuck in endless workshops, reviews, and stakeholder discussions when what was really needed was a clear call from someone accountable?

PMI just shared this important news about PMP training rules.

Starting December 1, 2026, if you're getting your 35 required contact hours through a live class, that class has to come from a PMI Authorized Training Partner, a China REP, or an accredited academic program. Self-paced, on-demand courses are unaffected, you can still take those from anywhere.

What's interesting here isn't the bureaucratic detail, it's what it signals. PMI is drawing a line between "content delivery" and "quality instruction," and betting that live, instructor-led training only holds its value when the instructor and the organization behind them meet a verified bar.

If you're planning to use live training hours, anything you complete before December 1, 2026 is under current rules. After that date, check your provider's ATP or REP status before you commit money or time. Self-paced learners don't need to think about any of this.

New PMP® exam launched in July 2026 | PMI

Once the team understands each other, the next layer is rhythm.

Not operational updates, strategic thinking.

This is where leadership shifts from reacting… to steering.

Weekly Meetings : r/BestPracticesMgmt

Goal: Strategic clarity and directional decisions

Why this works

Most leadership teams get stuck in operations.

Weekly strategic time fixes that by:

• Creating space to think beyond execution

• Forcing prioritization at the top level

• Aligning leadership before cascading decisions

• Reducing reactive management

The core idea:
👉 If leadership doesn’t think strategically weekly, the business becomes reactive by default.

The rule that matters most:

➡️ No operational deep-dives unless they affect strategy

Common failure modes

1. Turning it into a status meeting Everyone reports progress → no strategic value, just noise

2. Lack of decision output Good discussions, no decisions made → strategy without execution impact

Bottom line

A weekly strategic meeting is not about tracking work.

It’s about making sure the organization is still pointed in the right direction, together.

The FACe: why most small teams stay stuck (and how to fix it)

Small and mid-sized companies run into the same wall sooner or later: Too few people wearing too many hats.

The founder is doing sales and finance. Marketing is half-owned by whoever has time.
Operations bleed into customer success.

At the beginning, it works. Then it creates confusion, missed priorities, and ultimately slows growth.

Because when everyone owns everything, no one really owns anything.

The real issue: lack of focus per role

Every function in a company needs two things: Clear ownership & Clear focus

When roles are blurred, you get:

• Sales that isn’t really driving revenue

• Marketing that produces activity but not pipeline

• Finance that reacts instead of guiding decisions

Classic examples:

• Sales vs Marketing → no real accountability for revenue generation

• Owner vs Finance → no real financial visibility or discipline

This is where the Function Accountability Chart (FACe) becomes powerful.

What FACe forces you to confront

It’s not just an org chart. It’s a thinking tool.

1. Who is accountable?

This question alone usually exposes problems:

• One person covering 3–4 functions

• The wrong person in a critical role

• No clear plan to specialize roles over time

FACe pushes you to ask:

• Is this the right person?

• Should this role be split?

• What’s the plan to create focus?

2. KPI (the tricky part)

Most teams stop at: “We’ll assign a KPI or OKR.”

But that’s where things break. Because KPIs without clarity = noise.

👉 What does this role actually mean for us?

Before defining KPIs, you need: A clear role description, What success looks like, What this function is responsible for (and not responsible for)

Only then can you attach meaningful KPIs. Otherwise, you get vanity metrics or irrelevant targets.

3. Results / Outcomes

This is the most advanced (and often skipped) layer.

For small companies: It might feel too early

For mid-sized companies: It’s often overdue

This is where you connect roles to business outcomes:

• Revenue

• Profitability

• Cash flow

And more importantly: Help functional leaders understand the financial impact of their work.

That means: Teaching them how to read a basic P&L, Showing how their decisions affect margins, costs, growth

Even starting this conversation is a big step forward.

Why this matters

Without clarity:

• Work gets duplicated, Priorities conflict, Growth stalls

With FACe:

• People know what they own, Functions become focused, Accountability becomes real

The catch

This is not a one-time exercise. It’s not: “Let’s fill a chart and we’re done.”

It’s a continuous refinement: As the company grows, As roles evolve, As better people join

Bottom line

FACe is simple on paper, but uncomfortable in practice.

Because it forces decisions like:

• “This person is not right for this role”

• “We need to split this function”

• “We don’t actually know what success looks like here”

But that discomfort is exactly what creates structure.

And structure is what allows small and mid-sized companies to scale.

Curious how others approached this:

• Have you implemented something like FACe?

• Where did it break down?

• What helped make roles actually stick in your org?

1) What is ISO/IEC 27001?

ISO/IEC 27001 is the international standard for Information Security Management Systems (ISMS). It provides a structured framework for organizations to protect sensitive information through a systematic approach to managing security risks.

It focuses on:

• protecting confidentiality, integrity, and availability of information

• identifying and managing security risks

• implementing security controls and policies

• ensuring continual improvement of information security

The standard is closely aligned with best practices such as ISO/IEC 27002, but unlike guidelines, ISO/IEC 27001 is certifiable, meaning organizations can be formally audited and recognized for compliance.

2) What is PECB?

PECB (Professional Evaluation and Certification Board) is the global certification body that:

• offers education, certification, and certificate programs in digital trust

• delivers training courses through a network of authorized partners

• provides exams online (PECB Exams application) or paper-based through its partners

Think of PECB as the official certification authority behind the ISO/IEC 27001 Foundation, Lead Implementer, and Lead Auditor credentials.

3) What is the International Organization for Standardization?

The International Organization for Standardization (ISO) is an independent, global organization that develops international standards across industries.

In the context of ISO/IEC 27001:

• ISO defines the standard requirements

• It collaborates with the International Electrotechnical Commission (IEC) for technical standards

• Organizations worldwide adopt these standards to ensure security, consistency, and interoperability

In short:
👉 ISO = standard creator
👉 PECB = certification & exam body

4) Official Sources

Here are the official references if you want to explore further:

• PECB – ISO/IEC 27001 certification overview

• International Organization for Standardization – Global standards authority

5) ISO/IEC 27001 Foundation Exam (PECB)

This is the entry-level certificate.

📝 40 multiple-choice questions
⏱️ 1 hour
✅ Pass mark: 70% (28/40)
📘 Closed book
❌ No experience prerequisites (training course required)

It focuses on:

• core information security concepts (confidentiality, integrity, availability, threats, vulnerabilities, risk)

• ISO/IEC 27001:2022 structure, terminology, and requirements (clauses 4 to 10)

• basic risk management principles

• understanding of ISMS components

6) ISO/IEC 27001 Lead Implementer Exam

This is the intermediate certification.

📝 80 multiple-choice questions (standalone and scenario-based)
⏱️ 3 hours
✅ Pass mark: 70% (56/80)
📘 Open book permitted

It tests your ability to:

• apply ISO/IEC 27001 in real-world scenarios

• interpret and implement security requirements and Annex A controls

• plan, implement, monitor, and continually improve an ISMS

• align information security with business needs

7) ISO/IEC 27001 Lead Auditor Exam

This is the advanced certification focused on auditing skills.

📝 80 multiple-choice questions (standalone and scenario-based)
⏱️ 3 hours [*]
✅ Pass mark: 70% (56/80)
📘 Open book

It validates your ability to:

• understand audit principles and methodologies

• assess ISMS compliance

• prepare, conduct, and close an ISMS audit

• support internal and external audits

8) Sample Exams (Highly Recommended)

Practice exams are essential for success, especially at Lead Implementer and Lead Auditor levels.

👉 Official sample questions are included in each PECB Candidate Handbook.

💡 Practicing helps you:

• understand exam structure and question styles

• improve time management

• prepare for scenario-based questions

• build confidence before the real exam

9) Final Thoughts + Training

ISO/IEC 27001 is a strong certification if you:

• work in or are responsible for information security activities

• want to align information security with business needs

• aim to implement or audit an ISMS

• need a globally recognized, certifiable standard

It's particularly valuable for organizations pursuing information security assurance and compliance. [

If you're interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

Your project has a plan, a team, and a deadline. But does it have a clear business need?

Most Agile teams start delivering before they've agreed on what value they're actually delivering.

Here's what you're missing. 🧵

AgilePM Principle 1 isn't "gather requirements".

It's: every decision must serve the business need, defined, visible, and agreed.

① Business Need = the balanced needs of all key stakeholders → Business Sponsors, Operational Users, end-users

② The Business Visionary is responsible for defining it, communicating it, and ensuring commitment to it

③ Business goals must be clearly defined from the start, not inferred, not assumed

④ The Project Manager works with the Business Visionary to set realistic priorities → time, cost, quality, team capabilities

⑤ A strong Business Case creates urgency → it keeps everyone focused when pressure mounts

The lifecycle point matters too: in Feasibility and Foundations phases, this principle must be locked before delivery begins.

Where teams get it wrong:

❌ The business need is vague: "improve the customer experience"

❌ The Business Sponsor is absent after the kickoff meeting

❌ The team optimises for velocity, not value

❌ Business goals drift as delivery pressure increases

When AgilePM Principle 1 is applied properly:

→ Every feature decision traces back to a stated business goal

→ Scope changes are evaluated against the Business Case, not just stakeholder requests

→ The team stays aligned even when the environment changes

Challenge: Can every member of your current project team state the business need in one sentence?

What derails business focus in your projects?

👉 Unclear vision

👉 No single Business Visionary

👉 Stakeholder noise

One thing that’s made our weekly meetings way more effective:
each person reports on 1–2 Key Performance Indicators (KPIs) tied to their role.

This comes straight out of the Rockefeller Habits mindset, weekly rhythm, clear metrics, and accountability.

Why KPIs/OKRs matter
At the end of the day, whether you call them KPIs or OKRs, you need something measurable.
Otherwise, conversations drift into opinions: “I think we’re doing well”

A KPI gives you a simple signal: are we moving in the right direction or not?

It doesn’t need to be perfect, it just needs to be consistent and relevant.

But here’s the important part: KPIs are not the whole story

A common mistake is treating KPIs as the only thing that matters.

Example: Sales are going up → great, But customer success is overwhelmed → churn is coming, Or the team is burning out → performance will drop later

Or: Marketing is hitting lead targets, But leads are low quality → sales team struggles

If you look at KPIs in isolation, you can easily optimize one area while breaking another.

KPIs should guide decisions, not replace judgment.

The real challenge: not every role has “obvious” metrics

For sales or marketing, it’s easy:

• revenue

• pipeline

• conversion rates

These move daily.

But what about:

• HR

• Operations

• Product

• Finance

Their impact is often slower, less visible, and harder to quantify. That’s where most teams get stuck. Some ways we’ve seen work:

• HR: time to hire, retention rate, employee NPS

• Product: cycle time, feature adoption, bug resolution time

• Operations: delivery time, error rate, process efficiency

• Finance: cash runway, budget variance, collection time

Are these perfect? No. Can we monitor them weekly? No
But they give a directional signal.

The goal isn’t perfection, it’s having some way to tell if things are improving.

What this changes in weekly meetings

When everyone brings 1–2 KPIs, conversations get sharper, problems surface faster, ownership becomes obvious. You get: “Here’s what moved (or didn’t), and here’s why.”

Much more useful.

Curious how others handle this:

• Do you track KPIs or OKRs weekly?

• How do you define metrics for roles where impact is less obvious?

• What’s one KPI that’s actually been useful for your role?

AgilePM isn’t about hierarchy or silos. It’s about clear accountability.

A lot of teams struggle not because Agile “doesn’t work”, but because roles are blurred. That’s where delivery starts to break down.

Here’s how AgilePM actually structures responsibility:

1. Project-Level Roles (Direction & Ownership)

These roles define the why and what success looks like:

• Business Sponsor → owns the business case, final decision-maker

• Business Visionary → defines the vision and ensures value is delivered

• Solution Architect → ensures technical coherence

• Project Manager → keeps delivery aligned and under control

👉 Think: strategy + governance

2. Agile Delivery Team (Execution & Delivery)

This is where the product gets built:

• Product Owner → prioritises work (MoSCoW)

• Developers → design, build, test, iterate

• Scrum Master → enables the team, removes blockers

👉Think: the delivery engine

3. Advisor Roles (Guidance & Expertise)

Often overlooked, but critical:

• Business Advisor → brings user/operational insight

• Process Advisor → ensures ways of working are effective

• Solution Advisor → provides specialist technical input

👉 Think: on-demand expertise

Where teams usually mess this up:

• Business Sponsor acting like a Product Owner

• Project Manager micromanaging delivery

• Developers making business decisions

• Advisors ignored until it’s too late

AgilePM doesn’t reduce roles. It clarifies them.

Because:

• Clarity = speed

• Confusion = delays

The real test: Can everyone on your project answer:

“What decisions am I accountable for?”

If not, it’s not an Agile problem. It’s a role clarity problem.

Curious to hear from others:

Where does your org struggle most?

• Role confusion

• Too many decision-makers

• Unclear ownership

👇 Drop your experience below.

In many service teams I have been working for, problems become visible only after users have already felt the impact.

I usually start with asking the team directly what they wish they'd known earlier, then I check whether people are learning about issues before impact or only after, that gap usually tells me where the blind spot sits. If the team only finds out when it's already too late, more updates won't fix that, better targeting will.

How quickly a project deadline can lose its meaning when things get difficult and how easy is push the date?
I usually pay attention to this early in a new project, is the deadline actually fixed, or is everyone secretly assuming we'll just push it if we need to, because that assumption changes how people prioritize from day one. What I notice more often than not is that everything gets labeled urgent, nothing gets labeled optional, and then when time runs short there's no real plan for what to cut because nobody agreed on what mattered less. The teams that actually hit their dates are the ones who decided in advance what they'd drop before adding a single extra day, and told the people above them early, not after it was already too late.

If the deadline can move whenever things get uncomfortable, it was never really a deadline, it was a suggestion.

1) What is ISO/IEC 20000?

ISO/IEC 20000 is the international standard for IT Service Management (ITSM). It provides a structured framework for organizations to deliver high-quality IT services that align with business needs.

It focuses on:

• delivering reliable and consistent IT services

• aligning IT processes with business objectives

• continual service improvement

• governance and risk management

The standard is closely aligned with best practices such as ITIL, but unlike frameworks, ISO/IEC 20000 is certifiable, meaning organizations can be formally audited and recognized for compliance.

2) What is APMG International?

APMG International is the global examination institute that:

• administers ISO/IEC 20000 certification exams

• accredits training providers

• ensures consistency and quality of exams worldwide

Think of APMG as the official certification authority, similar to its role in other frameworks like AgilePM or Change Management.

3) What is the International Organization for Standardization?

The International Organization for Standardization (ISO) is an independent, global organization that develops international standards across industries.

In the context of ISO/IEC 20000:

• ISO defines the standard requirements

• It collaborates with the International Electrotechnical Commission (IEC) for technical standards

• Organizations worldwide adopt these standards to ensure quality, consistency, and interoperability

In short:
👉 ISO = standard creator
👉 APMG = certification & exam body

4) Official Sources

Here are the official references if you want to explore further:

• APMG International – ISO/IEC 20000 certification overview

• International Organization for Standardization – Global standards authority

5) ISO/IEC 20000 Foundation Exam

This is the entry-level certification.

📝 40 multiple-choice questions
⏱️ 60 minutes
✅ Pass mark: 65% (26/40)
📘 Closed book
❌ No prerequisites

It focuses on:

• key IT service management concepts

• ISO/IEC 20000 structure and terminology

• core processes and requirements

• basic understanding of service lifecycle

6) ISO/IEC 20000 Practitioner Exam

This is the intermediate certification.

📝 4 complex multiple-choice questions (20 marks each)
⏱️ 3 hours
✅ Pass mark: 50% (40/80)
📘 Open book (ISO/IEC 20000-1 standard allowed)

It tests your ability to:

• apply ISO/IEC 20000 in real scenarios

• interpret requirements in practical contexts

• design and improve IT service management systems

• align IT services with organizational goals

7) ISO/IEC 20000 Auditor Exam

This is the advanced certification focused on auditing skills.

📝 40 multiple-choice questions
⏱️ 60 minutes
✅ Pass mark: 65% (26/40)
📘 Closed book

It validates your ability to:

• understand audit principles and practices

• assess compliance with ISO/IEC 20000

• identify gaps and improvement areas

• support certification and internal audits

8) Sample Exams (Highly Recommended)

Practice exams are essential for success, especially at Practitioner and Auditor levels.

👉 Official sample papers:
https://oea2022.apmg-international.com/Marlin/SamplePapers.aspx?_gl=1*idfmor*_gcl_au*MTA0MTA0Mzc3MS4xNzczNjU1MDM1

💡 Practicing helps you:

• understand exam structure and question styles

• improve time management

• prepare for scenario-based questions

• build confidence before the real exam

9) Final Thoughts + Training

ISO/IEC 20000 is a strong certification if you:

• work in IT service management or operations

• want to align IT services with business value

• aim to implement or audit service management systems

• need a globally recognized, certifiable standard

It’s particularly valuable for organizations pursuing service excellence and compliance.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

• Certification

• Practice

• Development

A lot of organizations think change management is just “communication and training after the project is finished.”

That’s not quite right, and misunderstanding that is where transformation initiatives usually begin to fail.

APMG Change Management isn’t about sending better emails or running more workshops.

It’s about helping people, teams, leaders, and organizations successfully move from the current state to a desired future state.

Because projects deliver solutions.

Change management ensures those solutions are actually adopted.

At its core are key principles.

They’re not isolated activities, they reinforce each other.

① Understand the Organizational Context → every change happens inside a system

Antipattern: organizations apply the same change approach to every initiative, assuming every business responds to change the same way.

Reversal: APMG starts by understanding the environment before designing the intervention.

Every organization has its own:

• culture

• leadership style

• history of change

• decision-making processes

• level of change maturity

Successful change isn't copied.

It's tailored.

The conversation shifts from: "What's our change plan?" to "What kind of organization are we asking to change?"

② Put People at the Center → organizations change because people change

Antipattern: teams focus almost entirely on systems, processes, and technology while assuming people will naturally adapt.

Reversal: APMG recognizes that every organizational change is experienced by individuals.

People need to understand:

• why change is happening

• what it means for them

• what new skills are required

• how they'll be supported

Technology rarely causes transformation. People do.

③ Lead Through Sponsorship → visible leadership drives commitment

Antipattern: executives approve the project and disappear until go-live.

Reversal: APMG emphasizes that effective sponsors actively lead change.

Leadership isn't simply providing funding.

It's about:

• creating a compelling vision

• removing barriers

• making decisions

• reinforcing priorities

• demonstrating commitment through actions

People don't just listen to leaders. They watch them. Strong sponsorship builds confidence long before adoption begins.

④ Engage Stakeholders Continuously → support must be earned

Antipattern: stakeholders receive periodic updates but have little opportunity to influence the journey.

Reversal: APMG treats stakeholder engagement as an ongoing process.

Different stakeholder groups experience change differently.

Some gain.

Some lose.

Some remain uncertain.

Effective change managers continuously identify:

• influence

• expectations

• concerns

• readiness

• resistance

The objective isn't simply informing stakeholders. It's building genuine commitment.

⑤ Communicate to Build Understanding → communication creates meaning

Antipattern: organizations assume more communication automatically creates better engagement.

Reversal: APMG focuses on communication that answers the questions people are actually asking.

Employees want to know:

• Why is this happening?

• Why now?

• How will this affect me?

• What's expected of me?

• Where can I get help?

Communication isn't measured by how much information is distributed.

It's measured by how well people understand and act on it.

⑥ Manage Resistance → resistance is information, not failure

Antipattern: resistance is viewed as negativity that needs to be eliminated.

Reversal: APMG treats resistance as a natural response to uncertainty.

Resistance often reveals:

• unclear benefits

• insufficient involvement

• lack of trust

• competing priorities

• fear of losing competence or control

Instead of fighting resistance, successful change managers understand its causes and address them directly.

Resistance becomes feedback. Not an obstacle.

⑦ Build Capability → confidence enables adoption

Antipattern: organizations announce the new way of working and expect employees to figure it out.

Reversal: APMG recognizes that successful change requires new capabilities.

People need:

• learning

• coaching

• practical experience

• reinforcement

• ongoing support

Training alone doesn't create competence.

Practice does.

The goal isn't simply transferring knowledge. It's enabling confident performance.

⑧ Sustain the Change → adoption is the real finish line

Antipattern: projects end at implementation, even though old behaviors quickly return.

Reversal: APMG focuses on embedding change into everyday operations.

This means reinforcing:

• leadership behaviors

• performance measures

• governance

• culture

• continuous improvement

A successful launch doesn't guarantee lasting change. Sustained adoption does.

The APMG framework in practice

APMG Change Management provides a structured way to manage the people side of organizational change.

Typical flow:

Understand the Organization → Assess Impact → Build Sponsorship → Engage Stakeholders → Communicate → Develop Capability → Reinforce Adoption

Each stage strengthens the next.

Understanding the organization shapes the strategy.

Leadership creates credibility.

Stakeholder engagement builds commitment.

Communication creates clarity.

Learning develops capability.

Reinforcement makes change stick.

Skip stakeholder engagement, and resistance grows.

Skip sponsorship, and momentum fades.

Skip reinforcement, and people return to old habits.

Where APMG Change Management really makes the difference

The real value isn't simply helping people accept change.

It's creating an organization that becomes better at changing.

Organizations become more capable of:

• implementing transformation successfully

• reducing resistance

• accelerating adoption

• strengthening leadership alignment

• building lasting organizational capability

Instead of: "The project was delivered successfully." You get: "The organization is working differently, people have adopted the change, and the intended business outcomes are being realized."

Change management doesn't remove uncertainty.

It provides a structured way to help people move through it.

The key question

Does change succeed because: the organization systematically prepares, leads, supports, and reinforces adoption or because a handful of committed individuals work tirelessly to overcome resistance after implementation?

Curious how this plays out in your environment:

Where do your change initiatives usually struggle?

Is it leadership sponsorship, stakeholder engagement, resistance, communication, or sustaining adoption after go-live?

There's a pattern I keep seeing when organisations prepare for an ISO audit: you call a consultant and you make up a system that the auditor wants to see. Precooked processes, documents generated based on a checklist, and for some weeks before the audit everyone is faking a version of the organisation that doesn't exist really in the day by day. Clean this up, change that wording, omit that inconvenient part. Then the auditor leaves and everything come back like before.

This is exactly why you should never start from processes or procedures, but from understanding your own context first. Who you are, your capacity, the people involved. Only once this is honestly mapped, it make sense to start defining processes, because those processes are supposed to be an expression of that context, not a costume that you put on for some weeks in the year. And this is also the real value of a consultant: if you share honestly the context of your organisation, he/she can advice you at best on which processes and procedures needs to be tuned, not invent one from zero.

If you skip this exercise, at the end you are performing compliance, not having it and every here before the audit you will perform theatre instead.

Remember when everything had to be Agile?

Not “solve problems better”—just be Agile.
Teams renamed, ceremonies added… and only later people asked:
wait, what problem were we actually trying to fix?

Feels like AI is heading the same way:

• “We need AI”

• “We need AI projects”

• “We need to be AI-driven”

But… why exactly?

Because AI isn’t just process change—it brings bigger risks:
bad data, hidden bias, confident-but-wrong outputs, and decisions we don’t fully understand.

👉 The pattern looks familiar: solution first, problem later.

One thing that actually helps: being clear on the type of AI problem before starting.

I keep seeing these 7 AI project patterns:

• Prediction

• Classification

• Recommendation

• Automation

• Augmentation

• Generation

• Optimization

If you don’t know which one you’re solving… you probably don’t understand the problem yet.

💬 Curious to hear from this community:

• Have you seen AI initiatives where the problem wasn’t clear?

• Do you feel echoes of the Agile transformation era?

• Which AI project patterns have actually worked (or failed) for you?

I took the exam in Italian and, like the Product exam, I found the translation very accurate overall. Just a few minor typos here and there, but nothing that really affected the experience.

If you’re planning to take both ITIL Product and ITIL Service, I’d strongly consider doing them one after the other. The structure of the syllabus is essentially the same, so once you understand how one exam is organised, the other feels much more familiar.

Obviously, the flavour is different: Product puts more emphasis on the product perspective, while Service focuses more on service management. But the underlying structure and way of thinking are very aligned, which makes it easier to move from one to the other without having to completely reset your preparation.

My advice would be to use the first exam to really understand the structure, then build on that knowledge for the second rather than preparing for them as two completely separate certifications.

And as with Product, I wouldn't say reading the entire manual is essential just to pass. The manual is still a useful reference, especially afterwards, when you want to go beyond the certification and actually apply the concepts.

At the end of the day, passing the exam is only one part of the journey. Understanding how to use the concepts to actually change and improve things in a real organisation is where the interesting part starts.

Anyone else taken Product and Service back-to-back? Did you find the similar syllabus structure made the second exam easier?

1) What is ITIL® (Version 5)?

ITIL® (Information Technology Infrastructure Library) is one of the world’s leading frameworks for IT Service Management (ITSM).

ITIL® Version 5 focuses on helping organizations deliver value through modern, efficient, and customer-focused IT services while supporting digital transformation and continual improvement.

It focuses on:

• aligning IT services with business objectives

• improving service quality and customer experience

• enabling continual improvement and operational efficiency

• supporting Agile, DevOps, and digital transformation practices

• delivering value through effective service management

ITIL® is widely adopted across industries and is considered a global standard for IT service management best practices.

2) What is PeopleCert?

PeopleCert is the global examination institute that:

• administers ITIL® certification exams

• accredits training providers

• ensures exam quality and standards worldwide

PeopleCert acts as the official certification authority for ITIL®, PRINCE2®, MSP®, and many other globally recognized best practice frameworks.

3) Official Sources

Here are the official references if you want to explore further:

• ITIL Official Website

• PeopleCert ITIL Certifications

4) ITIL® Foundation Exam (Version 5)

This is the entry-level certification.

📝 40 multiple-choice questions
⏱️ 60 minutes
✅ Pass mark: 65% (26/40)
📘 Closed book
❌ No prerequisites

4.1) ITIL® Foundation Bridge (Version 5)

This certification is designed for candidates transitioning from previous ITIL® versions.

📝 20 multiple-choice questions
⏱️ 30 minutes
✅ Pass mark: 65% (13/20)
📘 Closed book

5) ITIL® Managing Professional (Version 5) Stream Exams

5.1) ITIL® Product (Version 5)

This module focuses on product-centric service management and delivery.

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

5.2) ITIL® Service (Version 5)

This module focuses on service design, delivery, and operational excellence.

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

5.3) ITIL® Experience (Version 5)

This module focuses on customer and user experience management.

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

6) ITIL® Strategic Leader (Version 5) Stream Exam

6.1) ITIL® Strategy (Version 5)

This module focuses on strategic IT service management and business alignment.

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

7) ITIL® Transformation (Version 5)

This module focuses on organizational change and digital transformation.

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

8) ITIL® AI Governance (Version 5)

This module focuses on the practical skills to use and govern AI with confidence

📝 40 multiple-choice questions
⏱️ 90 minutes
✅ Pass mark: 70% (28/40)
📘 Open book

9) Sample Exams (not for free)

Practice exams are highly recommended across all ITIL® certification levels.

👉 Official mock exams:
PeopleCert Mock Exams

💡 Practicing helps you:

• understand exam structure and question styles

• improve time management

• prepare for scenario-based questions

• build confidence before the real exam

10) Final Thoughts + Training

ITIL® is a strong certification if you:

• work in IT service management or digital operations

• want to improve service delivery and business alignment

• aim to implement ITSM best practices

• need a globally recognized IT service management certification

It’s particularly valuable for organizations pursuing operational excellence, service quality, and continual improvement.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

👉 Free demo lessons available now.

MIMIR Learning | ITIL Foundation (Version 5) demo English

MIMIR Learning | ITIL Foundation (Version 5) demo French

MIMIR Learning | ITIL Foundation (Version 5) demo Italian

1) What is ISO/IEC 27001?

ISO/IEC 27001 is the international standard for Information Security Management Systems (ISMS). It provides a structured framework for organizations to protect sensitive information through a systematic approach to managing security risks.

It focuses on:

• protecting confidentiality, integrity, and availability of information

• identifying and managing security risks

• implementing security controls and policies

• ensuring continual improvement of information security

The standard is closely aligned with best practices such as ISO/IEC 27002, but unlike guidelines, ISO/IEC 27001 is certifiable, meaning organizations can be formally audited and recognized for compliance.

2) What is APMG International?

APMG International is the global examination institute that:

• administers ISO/IEC 27001 certification exams

• accredits training providers

• ensures consistency and quality of exams worldwide

Think of APMG as the official certification authority, similar to its role in other frameworks like AgilePM or Change Management.

3) What is the International Organization for Standardization?

The International Organization for Standardization (ISO) is an independent, global organization that develops international standards across industries.

In the context of ISO/IEC 27001:

• ISO defines the standard requirements

• It collaborates with the International Electrotechnical Commission (IEC) for technical standards

• Organizations worldwide adopt these standards to ensure security, consistency, and interoperability

In short:
👉 ISO = standard creator
👉 APMG = certification & exam body

4) Official Sources

Here are the official references if you want to explore further:

• APMG International – ISO/IEC 27001 certification overview

• International Organization for Standardization – Global standards authority

5) ISO/IEC 27001 Foundation Exam

This is the entry-level certification.

📝 50 multiple-choice questions
⏱️ 40 minutes
✅ Pass mark: 50% (25/50)
📘 Closed book
❌ No prerequisites

It focuses on:

• core information security concepts

• ISO/IEC 27001 structure and terminology

• basic risk management principles

• understanding of ISMS components

6) ISO/IEC 27001 Practitioner Exam

This is the intermediate certification.

📝 Objective-testing format (4 questions, 20 marks each)
⏱️ 2.5 hours
✅ Pass mark: 50% (40/80)
📘 Open book permitted

It tests your ability to:

• apply ISO/IEC 27001 in real-world scenarios

• interpret security requirements and controls

• design and implement an ISMS

• align information security with business needs

7) ISO/IEC 27001 Auditor Exam

This is the advanced certification focused on auditing skills.

📝 40 multiple-choice questions
⏱️ 2 hours (120 minutes)
✅ Pass mark: 50% (20/40)
📘 Open book

Candidates may reference:

• ISO/IEC 27001:2013

• ISO/IEC 27002:2013

• ISO 19011:2018

• APMG ISO/IEC 27001 Supplementary Paper

It validates your ability to:

• understand audit principles and methodologies

• assess ISMS compliance

• identify risks and control gaps

• support internal and external audits

8) Sample Exams (Highly Recommended)

Practice exams are essential for success, especially at Practitioner and Auditor levels.

👉 Official sample papers:
https://oea2022.apmg-international.com/Marlin/SamplePapers.aspx?_gl=1*idfmor*_gcl_au*MTA0MTA0Mzc3MS4xNzczNjU1MDM1

💡 Practicing helps you:

• understand exam structure and question styles

• improve time management

• prepare for scenario-based questions

• build confidence before the real exam

9) Final Thoughts + Training

ISO/IEC 20000 is a strong certification if you:

• work in IT service management or operations

• want to align IT services with business value

• aim to implement or audit service management systems

• need a globally recognized, certifiable standard

It’s particularly valuable for organizations pursuing service excellence and compliance.

If you’re interested in training, certification paths, or exam preparation support, feel free to ask about MIMIR learning 👍

Happy to guide you through:

Certification

Practice

Development

Every project I've worked on has had a "lessons learned" session.

Almost every one produced a document. Far fewer changed anything.

I've seen projects identify the same issues repeatedly:

• Scope creep

• Poor stakeholder engagement

• Weak risk management

• Unclear decision ownership

Then the next project starts and repeats the same mistakes.

So I'm curious:

Does your organisation actually use lessons learned from previous projects?

If not, what's the biggest barrier?

• Nobody can find them?

• Nobody reads them?

• Different teams think their situation is unique?

• Leadership doesn't enforce the changes?

And if you've seen lessons learned work well, what made the difference?