How to Lead Every Personality Type on Your Team

 

Knowing your team's personality types is easy.

Leading to match their personality is the hard part.

The ones who build the strongest teams apply what they know.

Not as a templated style but tailored to each person and team.

Here's what that looks like in practice:

1. Match how you communicate to how they receive:

Drivers want the bottom line.
Thinkers want more context before the decision.

If you only work in one mode, you're losing half your team.

Action: Before your next 1:1, ask yourself, "Am I communicating in a way that suits them?"

2. Adjust how you share feedback to how they process:

Some people need to reflect on the feedback - in their own time.
Others want to talk through it at the moment.

Action: Observe and respect each person's preferred style. If they are quiet, ask if they would like to talk through it the next day.

3. Know how each person acts under pressure:

Everyone has a default different response to stress.

Some overwork, some overcompensate, and some need space.

When you know what pressure looks like on each person, it helps you notice it early.

Action: When you notice a team member under pressure, ask how you can support them.

4. Stop motivating everyone with the same thing:

Everyone wants (and deserves) to be valued.

But besides that, people have different needs: autonomy, promotion, being included in decisions, etc.

Find what drives each of them.

Action: Pick one person on your team and ask what motivates them.

5. Build your 1:1s around what each person needs:

A 1:1 shouldn’t be the same conversation with every person.

Some need space to think. Others need coaching, direct feedback, or help removing obstacles.

Action: Pick one team member this week and run your next 1:1 the way they prefer, instead of the way that feels natural to you.

Leadership is not one-size-fits-all.

People trust leaders who take the time to understand them and know how they work best.

The part I couldn't fit here: how to adapt your leadership style to each person without lowering your standards or looking inconsistent.

An incredible resource from my friend Cicely Simpson 🔥 (give her a follow)

https://lnkd.in/p/dsAkqVg6

Как провести годовую ретроспективу команды: 6 шагов и готовый фреймворк

 

Анна Ефимова

Ретроспектива помогает команде посмотреть на прошедший период чуть шире списка выполненных задач: понять, что стоит сохранить, какие проблемы повторялись и что хочется изменить дальше.

Такую встречу полезно проводить в конце года, но ждать декабря необязательно. Тот же подход подойдет после квартала, большого проекта или заметных изменений в работе команды.

Разбираемся, как проводить ретроспективу в команде, какие вопросы задавать и как не закончить встречу красивой доской из стикеров без единого решения. В конце — готовый шаблон, который можно скопировать и использовать со своей командой.

Что такое ретроспектива команды

Ретроспектива — встреча, на которой команда разбирает прошедший период или проект и отвечает на три главных вопроса:

• Что у нас работало хорошо
• Что регулярно мешало
• Что мы хотим делать по-другому в будущем

Главное отличие от обычного подведения итогов — ретроспектива помогает увидеть не что сделали, а как мы это делали.

Например, команда может выполнить годовой план. Но весь год сотрудники при этом узнавали о смене приоритетов в последний момент, по три дня ждали согласований и спасали проекты сообщениями «Есть минутка?» в 22:47. По цифрам год хороший, по процессам есть о чем поговорить.

💡 Для HR ретроспектива полезна еще и тем, что позволяет увидеть проблемы, которые плохо заметны в отчетах: перегрузку, неясные зоны ответственности, повторяющиеся конфликты процессов, нехватку обратной связи.

Когда стоит проводить ретроспективу

Необязательно ждать декабря и доставать шаблон ретроспективы вместе с гирляндой.

Наш шаблон рассчитан на итоги календарного года, но тот же фреймворк можно использовать после:

• Квартала или полугодия
• Большого проекта
• Запуска нового процесса
• Реорганизации команды
• Периода высокой нагрузки
• Серии изменений, эффект которых хочется оценить

Для короткого периода достаточно заменить шкалу января — декабря на нужные недели или месяцы. Остальная механика останется той же: вспомнить события → найти закономерности → выбрать изменения.

Как проводить ретроспективу в команде

Оптимально заложить 60–75 минут. Если участников много, лучше заранее предупредить, что встреча посвящена процессам команды, а не персональной оценке сотрудников.

Еще одно правило стоит проговорить вслух: обсуждаем ситуации и процессы, а не ищем виноватых.

Дальше можно идти по шести этапам.

Этап 1. Восстановите события года

Попросите каждого участника добавить на таймлайн два-три события:

• Главное событие года
• Лучший момент
• Самый сложный момент

Без таймлайна годовая ретроспектива легко превращается в ретроспективу ноября и декабря: мозг предпочитает свежий контент.

На этом этапе лучше ничего подробно не обсуждать. Сначала соберите общую картину.

Этап 2. Найдите, чем команда довольна

Следующий вопрос — что в работе команды в этом году сработало особенно хорошо и это стоит сохранить?‎

Можно смотреть на:

• Результат
• Скорость работы
• Качество
• Взаимодействие
• Процессы
• Новые навыки
• Решения, которые упростили жизнь

Важно не пропускать этот блок ради скорейшего перехода к проблемам. Хорошая ретроспектива должна показать команде то, что уже работает и что стоит сохранить.

Этап 3. Выявите дорогие процессы

Теперь вопрос сложнее — что в этом году стоило нам слишком дорого?

Речь не обязательно о деньгах. Процесс может дорого обходиться во времени, внимании и силах команды.

Например:

• Решения слишком долго согласовывались
• Задачи часто переделывали
• Приоритеты менялись быстрее, чем календарь
• Сотрудники тратили часы на рутину
• Важная информация регулярно терялась между людьми и чатами

На этом этапе лучше фиксировать конкретные ситуации.

Этап 4. Ищите повторяющиеся паттерны

Для годовой ретроспективы это один из самых полезных этапов. Посмотрите на все собранные стикеры и спросите: «Что происходило с нами снова и снова?‎»‎

Например, команда может обнаружить, что:

• В периоды высокой нагрузки постоянно ломается приоритизация
• Проекты зависают на одном и том же этапе согласования
• Сотрудники несколько раз за год поднимали одну проблему, но решение каждый раз откладывалось
• Некоторые процессы работают нормально в спокойные месяцы и рассыпаются, когда задач становится больше

Один неприятный эпизод может быть случайностью. Одинаковая ситуация в феврале, мае и октябре — повод заметить системную проблему.

Этап 5. Не пытайтесь исправить все

Когда проблем много, возникает естественное желание назначить ответственных за каждую и начать новую жизнь с понедельника. Лучше так не делать.

Сгруппируйте похожие наблюдения и проведите голосование. Например, дайте каждому участнику три голоса и попросите выбрать проблемы, которые, по его мнению, сильнее всего влияли на работу команды.

В работу достаточно взять два-три изменения.

Чем меньше изменений выбрала команда, тем выше шанс, что в следующем году кто-нибудь действительно вспомнит об их существовании и приложит усилия для исправления.

Этап 6. Закончите правилом 3-2-1

В нашем шаблоне финальный блок устроен по принципу:

3 — продолжаем делать. Что в работе команды уже хорошо работает и должно остаться.

2 — меняем. Два изменения, которые команда попробует внедрить в следующем периоде. Для каждого нужен ответственный и первый конкретный шаг.

1 — перестаем делать. Практика, процесс или привычка, от которых команда сознательно отказывается.

Так ретроспектива заканчивается не доской из сорока разноцветных стикеров, а коротким списком договоренностей.

Что делать HR во время ретроспективы

HR здесь полезнее в роли фасилитатора, а не человека с правильными ответами.

Следите, чтобы команда:

• Говорила о процессах, а не переходила на личности
• Приводила конкретные примеры
• Не тратила половину встречи на один эпизод
• Дошла до решений и ответственных
• Не набрала себе 20 улучшений одновременно

Если обсуждение застряло, можно возвращать участников к простому вопросу: на что из этого команда действительно может повлиять?

И еще: важная часть ретроспективы происходит уже после нее. На следующей встрече начните с прошлых договоренностей: что попробовали, что сработало, что нет. Иначе ретро рискует стать очень содержательным способом провести полтора часа раз в год.

Заберите готовый шаблон ретроспективы

В шаблоне уже есть таймлайн года, вопросы для обсуждения, зоны для стикеров, голосование и финальный блок 3-2-1.

Сделайте копию доски, пригласите команду и идите по этапам сверху вниз.

https://tinyurl.com/4xd3xefm

The Hook Model

 

Nir Eyal, a well-known author and behavioral economist, developed a four-phase process called the Hook Model that gives product teams a crisp, usable blueprint for designing repeatable user behaviors. Each stage of the process is rooted in decades of behavioral science: the triggers and prompts BJ Fogg mapped, Skinner’s research on reinforcement and reward patterns, Schultz’s insights into how dopamine responds to surprise, and Lally’s work on how tiny actions slowly harden into habits.

This piece explores the Hook Model through the lens of product design, not just what the model is, but why it works. We’ll connect each step to the academic research behind it and look at how real-world products turn these theories into experiences people return to again and again.

What is the Model?

At its core, the Hook Model is a four-step loop: Trigger → Action → Variable Reward → Investment. Repeated cycles nudge users toward automatic use: a well-placed trigger prompts an easy action, which may yield an unpredictable reward; the user then invests (time, data, social capital) that makes the next cycle likelier. Nir Eyal popularised this framework for designers, arguing that habits can lower acquisition costs and increase long-term retention when used responsibly.

Each stage of the process is grounded in its own body of behavioral theory, which we break down in detail below.

1. Trigger — external and internal

Triggers are cues that start the loop. External triggers (notifications, email, home-screen icons) are design artifacts; internal triggers are emotions, routines, or contexts that associate the product with a felt need. BJ Fogg’s Behaviour Model stresses that a trigger only works when motivation and ability are present — without those, the cue fails. Designers must therefore match triggers to the user’s current motivation and simplify the action to fit their ability.

A classic example is the Fitbit. Its external triggers: gentle wrist vibrations, step notifications, or progress nudges, cue the user to check their activity. But over time, those cues begin linking with internal triggers: moments of guilt after sitting too long, a burst of motivation during a walk, or the small thrill of closing a daily ring. Fitbit succeeds because the trigger aligns with a clear motivation (improving health) and the action is incredibly simple (glance at your wrist). The product doesn’t just remind users to walk; it gradually trains them to want to move, even before the vibration arrives.

2. Action

Action is the simplest behaviour performed in anticipation of a reward. Fogg’s Model gives a useful checklist: if motivation is low, reduce friction; if ability is low, simplify the interface; if both are low, redesign the task. Product designers should measure friction points (time to first meaningful action, number of taps, cognitive load) and iteratively reduce them.

For example, Whatsapp reduces friction to messaging (@mentions, slide to reply, etc.) so that the action of sending a message is immediate and habitual.

Source: growthengineering.co.uk

3. Variable Reward

Variable reward is the emotional payoff that keeps users returning. This principle is grounded in operant conditioning: variable reinforcement schedules (rewards given unpredictably) generate high, persistent rates of responding, the same principle that explains slot-machine persistence in behavioural psychology. Skinner’s work on reinforcement schedules and subsequent syntheses shows that partial, variable rewards produce stronger habit persistence than constant rewards.

At a neural level, dopamine signals a reward prediction error — the greater the positive surprise, the larger the dopamine response and the stronger the learning signal. Designing for small, variable surprises (novel content, social validation) leverages this mechanism.

Examples:

• Instagram: The feed delivers unpredictable, high-value content; the algorithm injects novelty so users experience frequent positive surprises.
• Duolingo: Variable points, streaks, and daily lesson difficulty produce small, unpredictable notifications and gratifications that feel rewarding.

4. Investment

Investment is the stage where users put something of their own into a product, whether it’s time, effort, information, or connections. These contributions make the product more valuable to them and naturally raise switching costs. When someone builds a playlist, completes their profile, or invites a friend, the experience becomes more personal and rewarding. For designers, the goal is to ensure these investments feel easy and worthwhile, so users immediately notice the benefits in their next interaction. This is ultimately what helps turn a one-time user into someone who keeps coming back.

As an example, Spotify encourages small investments (creating playlists, liking tracks) that personalize recommendations and make users more likely to return.

How do habits form over time?

Designers should be careful about known misconceptions or myths, “create a habit in 21 days.” Longitudinal research finds habit formation is gradual and variable: Lally et al. (2010) tracked real people adopting daily behaviours and showed that the time to reach automaticity ranged widely (often many weeks), and increases in automaticity follow a decelerating curve rather than a fixed threshold. In short: repeated, context-consistent triggers and rewards are necessary, there’s no fixed magic number.

Playbook

1. Map internal triggers. Interview users to surface emotions and contexts that should cue your product. (Fogg: trigger + ability + motivation).
2. Reduce friction for the core action. Measure and remove steps between trigger and reward.
3. Design variable rewards intentionally. Mix predictable utility (clear value) with intermittent surprises to sustain curiosity. (Skinner + Schultz).
4. Create investment moments. Design low-cost, high-value inputs that personalize the experience and increase future returns.
5. Measure automaticity, not vanity metrics. Track repeat-use in context and time to habitual use (daily/weekly retention, context-tied triggers) rather than raw installs. (Lally et al. suggest measuring increases in automaticity over time).

Ethics: hook versus help

Habit design sits on a moral fault line. When a product genuinely solves a problem, it can empower users; when it exploits vulnerabilities (compulsive consumption, attention hijacking), it harms them. Eyal himself and many designers urge building for mutual value: design hooks that improve users’ lives, disclose persuasive patterns, and provide graceful exits (controls and limits). Responsible habit design combines effectiveness with ethical guardrails.

Conclusion

The Hook Model is a compact, action-oriented synthesis of design practice and behavioural science. Its four stages: trigger, action, variable reward, investment, map neatly onto decades of research in persuasion, learning, and neuroscience. For product teams, the model is most useful when paired with empirical rigor: measure behaviour in context, validate which triggers and rewards actually change habits, and elevate ethical concerns above short-term retention wins. Built well, habit-forming products become useful routines; built poorly, they become frictionless traps, often causing harm to the user.

The 5 Questions

Nir Eyal offers 5 fundamental questions you should ask:

• What users really want, what their motivation is (internal trigger)
• How might we engage users with our product? (external trigger)
• What simple actions help users achieve their goals (action)
• How to satisfy users’ needs and show that “there is more” (reward)
• What work, effort users invest during this engagement? Does it load the next trigger? (investment)

Changing users’ behavior

There is one more aspect we should pay attention to: by applying this framework, we basically manipulate our users.

According to Eyal, we should ask these questions from ourselves:

• Would I use the product or service myself?
• Will the product help users improve their lives?

Major References:

• Nir Eyal, Hooked: How to Build Habit-Forming Products (2014). Gitter
• BJ Fogg. 2009. A behavior model for persuasive design. In Proceedings of the 4th International Conference on Persuasive Technology (Persuasive ‘09). Association for Computing Machinery, New York, NY, USA, Article 40, 1–7. https://doi.org/10.1145/1541948.1541999
• P. Lally et al., “How are habits formed? Modelling habit formation in the real world” (Eur. J. Soc. Psychol., 2010). https://onlinelibrary.wiley.com/share/TSWECMWAFFWDHSXGMB6Q?target=10.1002/ejsp.674
• B.F. Skinner, Schedules of Reinforcement https://www.bfskinner.org/wp-content/uploads/2015/05/Schedules_of_Reinforcement_PDF.pdf
• W. Schultz, “A neural substrate of prediction and reward” (Science, 1997). https://www.science.org/doi/full/10.1126/science.275.5306.1593

https://tinyurl.com/3bzrmscs

https://tinyurl.com/2vnj98cw

The Hook Model, developed by Nir Eyal in his book Hooked: How to Build Habit-Forming Products, is a 4-step behavioral design framework that companies use to build habit-forming digital products and drive repeat, voluntary engagement.

The 4 Steps of the Hook Model

• 1. Trigger (Триггер)
• External Triggers (Внешние): Cues in the user's environment that tell them what to do next (e.g., push notifications, email alerts, links, or ads).
• Internal Triggers (Внутренние): Cues that become hardwired into the user's brain through negative or positive emotions—such as boredom, loneliness, stress, or curiosity—causing them to open an app out of habit.
• 2. Action (Действие)
• The simplest behavior a user performs in anticipation of a reward (e.g., scrolling a feed, clicking a play button, or searching for a term).
• Based on BJ Fogg’s behavior model (B = MAP), this step requires sufficient motivation, ability (simplicity/low friction), and a clear trigger.
• 3. Variable Reward (Вариативная награда)
• Unlike predictable rewards, uncertainty triggers a spike in dopamine (based on B.F. Skinner's operant conditioning).
• Eyal divides rewards into three types:
• Tribe (Племя): Social rewards driven by connection, validation, and likes (e.g., social media feeds).
• Hunt (Охота): The search for information, resources, or content (e.g., web browsing, scrolling news).
• Self (Я): Mastery, competence, completion, or personal gratification (e.g., clearing an inbox, finishing a level).
• 4. Investment (Инвестиция)
• The user puts something of value into the product (time, data, effort, social capital, or money).
• This investment loads the next trigger, stores value (e.g., building a profile, saving playlists, accumulating followers), and increases the likelihood that the user will return for another cycle.

Core Purpose & Ethics

• The Goal: Shift users from relying on expensive external marketing to responding automatically to internal emotional triggers ("first-to-mind wins"), creating sustainable retention and lower customer acquisition costs.
• Habit vs. Addiction: Eyal distinguishes a healthy habit (frequent, low-conscious behavior that benefits the user) from addiction (pathological behavior that harms the user).

 

In his books Hooked and Indistractable, Nir Eyal addresses a critical dilemma: product designers have mastered the ability to manipulate human behavior, meaning they have a moral responsibility to use that power ethically.

To prevent companies from building addictive or harmful products, Eyal introduces two primary ethical frameworks: The Manipulation Matrix and The Regret Test.

1. The Manipulation Matrix

The Manipulation Matrix is a 2x2 grid designed to help product creators evaluate their underlying motivations. It forces a founder or designer to ask two fundamental questions:

1. Materially Improve: Does the product materially improve the user’s life?
2. Use: Does the creator use the product themselves?

Based on the answers to these questions, creators fall into one of four quadrants:

🟢 The Facilitator (High Benefit, High Use)

• Criteria: The product materially improves lives, and the creator uses it regularly.
• Analysis: This is the highest ethical standard. Because you use your own creation, you intimately understand its friction, its potential to overwhelm, and its actual utility. There is no hypocrisy here. Eyal argues that creators operating as Facilitators have the highest chance of long-term success because they design with genuine empathy.
• Examples: A fitness app built by an athlete to track their own workouts, or a budget tracker used daily by its engineering team.

🟡 The Peddler (High Benefit, Low Use)

• Criteria: The product materially improves lives, but the creator does NOT use it.
• Analysis: This is common in B2B software, healthcare, or education, where a healthy adult might build software for children, patients, or a specific niche profession. While well-intentioned, the danger here is a lack of empathy. Because you don't use it, you might easily misjudge how annoying a notification is, or how exhausting a feature's loop might feel over time.
• Examples: A software developer building an app to help diabetes patients manage insulin doses.

🟡 The Entertainer (Low Benefit, High Use)

• Criteria: The product does NOT materially improve lives (in a utilitarian sense), but the creator uses it for fun.
• Analysis: This quadrant covers the gaming, streaming, and entertainment industries. Entertainment is an essential part of life, but it doesn't structurally improve a user's health, wealth, or wisdom. The ethical risk here is sustainability; entertainment products operate on a "hit-driven" model. If the creator stops enjoying it, the userbase will likely burn out and leave soon after.
• Examples: Mobile casual games, movie streaming platforms, or immersive fiction apps.

🔴 The Dealer (Low Benefit, Low Use)

• Criteria: The product does NOT improve lives, and the creator does NOT use it.
• Analysis: This is purely exploitative behavioral engineering. The creator acts exactly like a drug dealer—hooking users on a loop that damages their wellbeing, while carefully avoiding consumption themselves to stay clean. This relies on "dark patterns" designed purely for monetization via behavioral vulnerability.
• Examples: Online slot machine games, predatory gambling apps, or hyper-addictive social platforms designed exclusively to extract ad revenue while harming user mental health.

2. The Regret Test

As tech matured, Eyal realized the Manipulation Matrix wasn't enough on its own. A creator could easily rationalize that they are "Facilitators" while still building harmful loops. To fix this loophole, he introduced The Regret Test in his later work.

The Regret Test shifts the focus from the creator's intent to the user's reality. It is defined by a simple thought experiment:

"If the user knew everything that the designer knew about how the product is engineered to keep them hooked, would they still choose to use it? Or would they regret the time and money they spent?"

How to Conduct a Regret Test

To apply this test, a company must bring in a representative sample of users and openly tell them the tricks being used behind the scenes.

• If you tell a user: "We use a variable reward algorithm that intentionally delays showing you your notifications for 5 minutes so that you get an anxious spike and open the app more often," how do they respond?
• Ethical Design: The user says, "Ah, I see how it works, but I still love the value I get from this platform, so I will keep using it."
• Manipulative Design: The user feels cheated, angry, and says, "Wow, you are tricking me into wasting my life. If I knew that, I would delete this app."

If your product's engagement metrics rely on users feeling regret after the fact, the habit loop is unsustainable and unethical.