Career and Management Skills

Who this lecture is for

Built for HR and learning managers running development weeks and internal career days, for organisations where open roles keep going to external candidates, and for managers of large teams whose strongest people have plateaued and started taking calls from recruiters. Employee welfare committees book it for content days. It also fits women's forums and graduate programmes inside companies, public sector bodies and hospitals with rigid tenure tracks, and tech organisations where promotion budgets froze and the room deserves an honest conversation.

Questions about this lecture

We have no open positions right now. Will the session leave people expecting a promotion we cannot give?

No. It is built on the opposite premise, that advancement is not always available on demand, and it says so out loud. People work on what they can control, the evidence they are building, the scope they can take inside the role they already have, and readiness for the moment a position does open. Nothing in it asks the organisation to promise anything.

Does it separate growing as a specialist from moving into management?

Yes, and that fork is treated as a real decision rather than a default. Plenty of strong professionals drift toward a management title because it looks like the only visible way up, then discover the job they actually wanted was a deeper specialist track. Participants leave able to name which of the two they are aiming at and what evidence each one demands.

Is this a motivational talk, or do people leave with something they can use?

The second. The core of it is the case an employee has to make, what counts as evidence at the next level, how it gets written down, and who needs to hear it before the decision is even discussed. Motivation without a case is exactly what leaves people frustrated the following week.

Our last promotion round was frozen and the room is cynical. Will this backfire?

Cynicism after a frozen round is addressed directly rather than talked around. A room that has been disappointed will not accept optimism, so the starting point is how these decisions are really made, including budget timing and who sponsors whom. Naming the mechanics honestly lowers the temperature far more reliably than encouragement does.

Does the session get into salary, or is that deliberately left out?

Pay is acknowledged as the thing everyone in the room is thinking about, but it is not the centre of the session. Advancement and compensation are decided by different mechanisms on different calendars, and treating them as one conversation is a common reason evaluation meetings collapse into an argument. Participants get the advancement side, clearly separated from the money side.

Who this lecture is for

Written for HR and learning managers in mid-sized and large companies opening a manager development track, and for organisational development units buying a single session rather than a full in-house programme. It is equally aimed at the buyer this market ignores, the owner or chief executive of a smaller business who has just promoted their first team leads and has no HR department standing behind them. It also fits management forums, annual management conferences, and public sector and health fund HR units running manager cohorts.

Questions about this lecture

Our new managers were promoted because they were the best professionals on the team. Will the session imply they were wrong to keep doing the work?

The opposite. Being excellent at the craft is the reason they were chosen, and that is said plainly. What changes is where their output now comes from. The pull back toward hands-on work is treated as a predictable reflex rather than a character flaw, which is what makes managers willing to admit to it in the room.

How do you handle a manager who now leads people who were her friends and peers last month?

That situation sits at the centre of the session rather than in a footnote. The awkwardness does not get solved by pretending the friendship never existed, or by overcorrecting into cold distance. The work is on naming the change out loud with the person, and deciding where the line now sits on information, favours and criticism.

Several of our managers lead people who are older and far more experienced than they are. Is that addressed?

Yes. A young manager leading a veteran is common in Israeli companies and it fails in a specific way: the manager either avoids giving direction at all or overplays authority to compensate. The session works on setting expectations with an experienced report while genuinely drawing on that experience, which is usually what the veteran wanted in the first place.

We are a small company with no HR function and no formal review cycle. Is this still relevant?

It is aimed at exactly that reality. Most management content quietly assumes a review system, a career ladder and an HR partner in the background. Here the assumption is a manager with a handful of people, no process to lean on, and decisions that have to be made in conversation rather than through a form.

How is this different from manager development programmes that run for many sessions, and when should we buy those instead?

A long programme reshapes how a manager thinks over months, and nothing shorter can claim that honestly. What a single session can do is give a cohort shared language and a few concrete moves for the situations in front of them right now. If your managers are already inside a structured track, this works better as a sharp addition to it than as a replacement for it.

Who this lecture is for

For HR and organisational development managers assembling a senior or middle manager cohort, and for executive teams preparing for a board, an investor meeting or an appearance in front of a parent company abroad. It fits organisations with client-facing and stage-facing roles in sales, pre-sales, customer success and product, where presence is part of the job description. Women in management programmes book it under that heading, and professional associations and management forums use it as the content slot at a members evening.

Questions about this lecture

We already ran a presentation skills course. How is this different?

A presentation course prepares you for a moment you own, with a deck and an audience that came to listen. Managerial presence is about the rooms you do not control, where you speak briefly, without preparation, against someone more senior. The two overlap less than people assume, which is why managers who present beautifully still get talked over in the management meeting.

Our managers are told to show more presence in reviews and nobody can define it. Can you turn it into something observable?

That is the core of it. Presence gets broken into things a colleague could actually watch you do, how you enter a discussion, what you do when challenged, how heavily you qualify what you say, whether you finish a sentence or let it trail off. Once it is behaviour, a manager can practise it and a reviewer can point at it.

How do you handle a genuinely introverted manager? Are you asking them to become someone else?

No, and a session that tries usually produces a worse manager. Volume and extroversion are not the mechanism. Quiet people often carry more weight in a room precisely because they speak less, provided what they do say lands where it counts. The work is on placement and clarity, not on turning the personality up.

Several of our managers present to a parent company abroad in English. Is that covered?

Yes, because the presence penalty of switching out of your first language is real and almost nobody discusses it. Sentences get simpler, hedging goes up, and confident people start sounding tentative. The session deals with holding authority when your vocabulary is narrower than your thinking.

Does it deal with how a manager comes across in writing, or only in the room?

Writing is included, because in most Israeli companies a great deal of the impression is formed in email and chat rather than in meetings. A message fired off at speed, with too much apology or too many exclamation marks, quietly undoes what was built in the room. Written presence is treated as the same skill in a different medium.

Who this lecture is for

Aimed at HR managers booking for mid-level and senior management, and at procurement, supply chain, finance and legal teams who negotiate daily with no shared method, so outcomes depend on who happens to be in the chair. Sales and account teams treat it as a revenue skill. It is written just as much for the buyer this market skips, the owner of a small or mid-sized business who negotiates with suppliers, landlords and clients personally, with no procurement function standing behind them.

Questions about this lecture

Our people negotiate mostly inside the company, over budget and priorities, not with suppliers. Is that covered or is this a procurement course?

Internal negotiation is the spine of this session, not an appendix. The hardest negotiations most employees face are with another department, with their own manager, and with a colleague whose cooperation they need and cannot order. Supplier and client situations appear as examples where they help, but the default room is your own building.

Will employees leave this session and immediately come asking for a raise?

Some will ask sharper questions about scope and workload, which is usually healthy. On the pay side the emphasis is preparation and evidence rather than pressure, so the conversations that do happen tend to be more concrete and considerably shorter. Organisations that fear this question are often the ones where it is already being discussed, just not with a manager in the room.

Some of our managers think negotiation means being aggressive and it clashes with our culture. How is that handled?

It gets raised early, because that objection quietly kills the session if it stays unspoken. Aggression is a symptom of poor preparation rather than a technique, and the people who concede most are often the ones performing toughness. The work is on preparation, options and what happens if there is no agreement, none of which requires raising your voice.

Do participants practise on their own real cases, or on invented scenarios?

Real ones work far better, and people walk in carrying them anyway. A live case someone is dreading next week produces more honesty than any invented scenario about buying a car. Sensitive material stays in the room, and anyone who prefers a neutral example is free to use one.

What do you offer the person who genuinely avoids confrontation?

Most of the room is that person, which is why negotiation is not framed here as a contest of nerve. Preparation carries the weight, deciding in advance what you are asking for, what you are willing to trade and where you stop. Someone who dislikes conflict but arrives prepared routinely outperforms the confident improviser.

Who this lecture is for

Booked mainly by HR and welfare functions looking for content that prevents burnout rather than marking it after the fact, and by high-load operational organisations, hospitals and medical teams, call centres and service floors, emergency and security bodies, where the pressure is structural and permanent. It also fits companies that describe the problem as a time problem, where days fill up and nothing important moves. Executive teams take it as a performance session rather than a wellbeing one, and kick-off days use it as the substantive hour.

Questions about this lecture

Our overload is structural. How do you teach coping without implying it is the employee's fault for not being resilient enough?

By naming the split out loud at the start. Part of the load is created by how the organisation assigns work, sets deadlines and interrupts, and no breathing technique touches that. What an individual controls is smaller but real, and it is presented as such. Rooms visibly relax once they hear nobody is about to be told to meditate their way out of an understaffed quarter.

We already did a wellbeing session. People liked it and nothing changed. Why would this be different?

Because enjoying a session and changing a behaviour are unrelated events. The test here is whether one small thing is still happening weeks later, so the content stays deliberately narrow, a handful of habits chosen because they survive a bad week. Breadth is precisely what makes wellbeing content evaporate by Thursday.

Does it deal with the constant chat and phone interruptions, which our people say is what actually kills their focus?

Yes, and as the main mechanism rather than a side note. Israeli workplaces run on immediate response, so the useful question is not how to concentrate harder but which messages genuinely need an answer now, and how a team agrees on that together. Individual discipline against a group norm loses every single time.

Is there a part for managers, given that a manager can protect or destroy a team's capacity by how they assign work?

The manager side is included, because most of what exhausts a team is decided above it. Where work lands, how often priorities change, whether the calendar leaves any gaps to actually work in, whether messages arrive at night. A room of employees alone will only ever fix a fraction of the problem.

Our teams have people absent on reserve duty and others covering for them. Is that reality addressed?

It is, because absorbing a sudden absence is a normal Israeli operating condition rather than an exception. The practical issue is what the covering person stops doing, since nobody holds two jobs indefinitely, and that is a decision the manager and the team have to make explicitly rather than letting it default to whoever is most willing to suffer.

Who this lecture is for

Built for HR and training managers assembling a management development day for first-line and mid-level managers, and for the chief executive or VP HR opening or closing a management offsite. Organisational consultants and internal development units book it as a guest module inside a longer manager track. Welfare and events coordinators use it as the headline session at an annual conference. It also fits public sector and health fund training units, and chambers, incubators and accelerators running founder and manager cohorts.

Questions about this lecture

How do we stop the same decision from being reopened at every management meeting?

Usually it was never actually closed, only discussed until the meeting ended. A decision that survives needs a named owner, a stated basis, and an agreed trigger that would justify revisiting it. Without that last piece, anyone who is unhappy can reopen the subject simply by feeling differently this week, and eventually everybody does.

How much information is enough? Our managers keep waiting for more.

The useful question is not how much information exists but what would actually change if you had it. If a new piece of data would not change the choice, gathering it is procrastination with a spreadsheet attached. There is a practical way to test that, plus the harder discipline of setting the deadline for the call before the analysis begins.

Our managers escalate everything upward because nobody wants to be blamed for a wrong call. Is that addressed?

Directly, because it is a system problem wearing a personality costume. Where only outcomes are judged, escalation is the rational move for any careful manager. The work is on judging the reasoning at the time the decision was made, which is what makes it safe to decide at the level where the knowledge actually sits.

What changes when the pressure is financial, a cash gap or a frozen budget, rather than operational?

The clock changes and so does the order of the questions. A financial squeeze narrows options faster than an operational one and punishes delay much harder, so the sequence becomes exposure first, reversibility second, preference last. This is the angle most decision content skips entirely, and it is where a business consulting view differs from a psychological one.

How should decision authority be split between a manager and the team? Which calls do I delegate and which do I keep?

Reversibility is the cleanest test available. Calls that are cheap to undo belong as low as possible, where the knowledge is, and a manager who keeps taking them back trains the team to stop thinking. Expensive, hard-to-reverse calls stay with the manager. Saying out loud which is which removes most of the friction that otherwise gets read as a trust problem.

Who this lecture is for

For HR and training managers commissioning a first-line manager track, and for VPs and department heads buying an intervention for one specific team that has stalled or has just been merged into another. Team leaders and project managers in tech and industry who own a cross-functional group without authority over its members are a core audience. It also fits founders whose team doubled and whose informal coordination stopped working, welfare coordinators weighing a bonding day against a working session, and health funds and municipalities running manager cohorts.

Questions about this lecture

Our team already had a bonding day and nothing changed. Why would this be different?

A bonding day buys goodwill, which is real but perishable. It does not decide who owns which interface, whether feedback happens before the annual review, or what is done about the person everyone works around. This session is about those mechanisms. Both purchases have their place, as long as nobody expects the first one to do the job of the second.

How do we measure whether anything changed? The word measurable gets used a lot with no method behind it.

Use indicators the manager can already see. How long a typical piece of work takes from start to delivery, how often a decision gets reopened, and whether the people you would hate to lose are still there. None of them requires a new system, all of them move when the underlying problem moves, and taking the reading before the session is what makes the comparison mean anything.

How do I handle the one underperformer everyone tolerates, without losing the rest of the team?

That person usually costs more than they appear to, because the strong performers absorb the difference and quietly resent it. It runs as a sequence: name the gap specifically rather than generally, agree what changes and by when, and decide in advance what happens if it does not. Most managers skip the first step, then wonder why the conversation went nowhere.

Does this work for a cross-functional team where the manager has no formal authority over the members?

Yes, and that is the harder version of the job. Without authority everything rests on clarity of interfaces, on making commitments visible to the people who do hold authority, and on being the one who removes obstacles rather than the one who chases status updates. Managers with formal authority need the same discipline. They simply get away with more when they skip it.

How do we design the team so a sudden long absence does not stop the work?

By treating single points of dependency as a design flaw rather than as loyalty. A sudden call-up, a long illness and a resignation all expose the same weakness: one person holding knowledge nobody else has. The practical work is finding where that is true and deciding what gets written down or shared before the absence arrives, not during it.

Who this lecture is for

Bought mainly by HR and organisational development managers who want an employee-facing session that quietly serves internal mobility and retention, and by welfare coordinators looking for content staff will genuinely value. Employer branding and talent acquisition teams book it to get employees and recruiters visible and credible online. It also fits career centres at colleges, employment centres and municipal employability programmes, professional associations and alumni networks running member evenings, and companies in restructuring who want to offer real career support on the way out.

Questions about this lecture

If we teach our employees personal branding, are we not helping them leave faster?

It is the right question and the market avoids it. People leave when they cannot see a path, not when they can describe their own value. Most of this session points inward, at how an internal move is found and won, which is the cheapest retention there is. An employee who can name what they want is far easier to keep than one who only knows they feel restless.

How do you handle employees who find self-promotion distasteful and simply refuse to do it?

By dropping the word. What decides internal advancement is whether the people in the room can describe your work when you are not there, and that is built by making the work legible, not by talking about yourself. Quiet professionals tend to accept that framing, because it asks them to be clearer rather than louder.

Does this require LinkedIn? Some of our roles are not public-facing and our sector limits online exposure.

No. The online half is optional, and the offline half is what decides promotions in Israeli companies anyway, how you are spoken about internally, who knows what you can do, and whether you are remembered when a project is being staffed. Public profiles are covered for those who can use them, but nothing here depends on one.

What do you tell mid-career people whose work is being reshaped by AI?

That job titles are becoming a poor description of what someone can actually do, which is exactly why stating your capability separately from your role is worth more now than it used to be. The work is on identifying which part of your value is durable judgement and relationships, and which part was simply a set of tasks.

Should our team leaders attend too, since they are the ones who have to run the career conversation afterwards?

Ideally yes. The usual failure is an energised employee arriving at a manager who has no idea what to do with the conversation and no authority to promise anything. A manager who has heard the same material can answer with something concrete instead of deflecting, which largely decides whether the session produces movement or just noise.