Who is the Pekulav leadership programme designed for?

The programme is designed for working professionals who already hold some leadership responsibility and want to develop more deliberate, practical skills - not for those starting from zero.

How much time does participation require each week?

Participants should expect to commit roughly four to six hours per week, including live sessions, independent work, and peer exchanges.

Is prior formal education in business required?

No formal business qualification is required. Selection is based on professional experience and the quality of the application, not academic credentials.

Business Leadership Masterclass

Leading with clarity in uncertain conditions

Pekulav brings experienced practitioners together with working professionals to examine how leadership decisions actually get made - not in theory, but under real constraints.

Professional development environment at Pekulav

Who belongs here

A specific kind of participant fits this environment

This programme draws people who are already carrying leadership responsibility - team leads, department heads, founders managing their first hires - and who have noticed that the informal habits they built early are starting to show their limits. The content assumes professional context, not academic background.

Participants arrive with at least three years of direct people management or organisational decision-making behind them. They are not here to learn what leadership is. They are here because they have encountered situations where their current approach did not produce the result they expected.

Team leads and managers Responsible for at least one direct report and navigating day-to-day team dynamics.

Founders in early growth Building structure for the first time, often without a management background.

Senior contributors stepping up Moving from individual performance into accountability for a group's output.

Not a fit Those seeking motivation, general career advice, or introductory management theory.

Leadership skills development in practice

The distance to cover

Knowing what to do and doing it under pressure are different problems

Most experienced professionals can describe good leadership. Fewer can sustain it when a team member goes quiet in a critical week, when a stakeholder shifts expectations mid-project, or when two capable people on the same team stop cooperating. The gap is not knowledge - it is practice under realistic conditions.

Pekulav sessions are built around documented situations drawn from actual organisations. Participants work through decisions with incomplete information, competing priorities, and time constraints - the same conditions they face at work. The distance between where someone starts and where they finish is measured in changed behaviour, not completed modules.

The concern about time commitment

The most common reason experienced professionals hold back is not cost or doubt about the content - it is the calculation of hours. Four to six hours per week for twelve weeks is a real number, and it lands differently depending on what someone's calendar already looks like.

Sessions are scheduled across two fixed weekly slots, with recordings available for the rare week when attendance is not possible. The independent work between sessions is structured, not open-ended - each task has a defined scope and a clear output. Most participants report that the discipline of protecting those hours produces a secondary benefit: it forces a degree of prioritisation they had been avoiding.

There is no version of this programme that requires less commitment and delivers the same result. The time is part of what makes it work.

After completion

What becomes possible at the end

Graduation is not a certificate moment. It is a point at which participants have worked through enough real situations that their default responses have started to change. These are the practical shifts that participants and their managers most commonly report.

Clearer decision framing

Participants develop a consistent method for separating what is actually being decided from the noise around it - reducing the time spent in ambiguous holding patterns.

Difficult conversations held earlier

The avoidance pattern that lets small problems compound is one of the most common things participants name as changed. Not eliminated - but moved earlier in the cycle.

Team accountability without micromanagement

Participants leave with a working structure for holding people to commitments without needing to be present for every step - which is where most early managers get stuck.

Stronger peer relationships

The cohort structure means participants finish with a group of peers at a similar career stage who have worked through real problems together - that network has practical value.

Legible leadership presence

Teams respond to leaders who are consistent and readable. Participants work explicitly on the signals they send - in meetings, in writing, and in how they handle setbacks.

A documented body of work

Each participant produces written analysis and decision frameworks across the twelve weeks - a portfolio of thinking that can be referenced and built on after the programme ends.

What participation involves

Structure, cost, and what is included

The programme runs across twelve weeks in cohorts of fourteen to eighteen participants. Two live sessions per week run at fixed times with full recordings kept for ninety days. Between sessions, participants complete structured written tasks and one peer exchange per fortnight.

Pricing is published on the learning programme page along with the current cohort schedule. There is no instalment option for the standard enrolment, though a limited number of deferred-payment places are available each cohort - these are allocated on application, not on a first-come basis.

All facilitation is conducted by practitioners with active leadership roles, not career educators. The selection process for facilitators is the same as for participants - demonstrated experience in the specific situations being discussed.

Twelve weeks - two live sessions weekly, structured peer work, and a written portfolio produced throughout.

Four to six hours per week - sessions are recorded, independent tasks are scoped and time-bounded.

Cohorts of 14–18 - small enough that facilitators know each participant's specific context.

From participants

Specific accounts from people who completed the programme

Aoife Brennan

Operations Lead, Dublin

"Before the programme I was managing by instinct and hoping the team would fill in the gaps. The written tasks forced me to articulate what I was actually doing - and that was uncomfortable in a useful way."

Rafał Wysocki

Founder, Warsaw-based product studio

"I kept promoting the wrong people because I was measuring contribution instead of capability to lead others."

Before

Three hires in eighteen months that required replacement within a year. Promotion decisions made on gut feeling.

After

A structured assessment approach for internal moves. Two promotions since completing the programme - both still in role.

Siobhán Ní Fhaoláin

Department Head, Cork

"I had been waiting for the right moment to raise a recurring performance issue with one team member. The right moment never came - until the programme made it clear I was the reason it kept being delayed."

The situation

Eight months of documented concern, no direct conversation, team morale affected by the inconsistency.

The change

Conversation held in week seven of the programme. Issue resolved within a month. Team dynamic measurably improved.

Tomasz Górecki

Senior Manager, Galway

"The peer cohort was something I underestimated going in. Working through the same scenarios with people from different industries meant the solutions were less obvious and more transferable."