Soqratic Sandbox

Category: Leadership

  • The Complete Guide to Leading Remote Teams

    Leading a remote team is not leading an office team over video. The habits that work in a shared room, such as noticing who looks stuck or settling a question in the corridor, disappear, and they have to be replaced deliberately. This guide collects what we have seen work across forty remote teams we have coached.

    Start with outcomes, not hours

    Remote teams fail quietly when managers keep measuring presence instead of progress. The first shift is to agree, in writing, what done looks like for each piece of work and when it is due. Once outcomes are explicit, nobody needs to prove they are busy, and the manager stops refreshing chat to see who is online.

    Write the outcome as a sentence a stranger could check: the onboarding guide is published and two new hires have followed it without help. Avoid outcomes that are really activities, such as work on the onboarding guide. Activities can go on forever; outcomes end.

    Default to writing

    A distributed team runs on written context. Decisions, the reasons for them and the options that were rejected belong in a shared document, not in a call that half the team missed. Writing is slower in the moment and much faster over a quarter, because nobody has to reconstruct why something was decided.

    Keep a decision log with four columns: the decision, the date, who made it and why. Link to it from the project page. When someone asks why we did this, the answer is a link, not a meeting.

    • Decisions and their reasons go in the decision log.
    • Status goes in a weekly written update, not a standing meeting.
    • Questions that need discussion get a short document first, then a call if the comments do not settle it.

    Design meetings for the time zones you have

    If your team spans more than six hours, there is no meeting time that is fair to everyone, so rotate the inconvenient slot rather than always giving it to the same people. Record anything with decisions in it, and post a written summary within the hour so the people who were asleep can still object.

    Cut the recurring meetings that only exist to share status. Keep the ones where people need to think together: planning, retrospectives and one-on-ones.

    Make one-on-ones the backbone

    In an office, managers pick up problems in the corridor. Remotely, the one-on-one is the corridor. Hold it every week, never cancel it to make room for something else, and let the report own the agenda. The manager brings two standing questions: what is getting in your way, and what would you like more or less of from me.

    Keep a shared running document for each report, newest meeting at the top. It becomes the record of commitments on both sides and makes performance conversations evidence-based instead of a matter of memory.

    Protect focus time

    Remote work promised fewer interruptions and delivered more of them, because every message arrives in the same place as every deadline. Agree team norms: which channels need an answer the same day, which can wait until tomorrow, and which hours are protected for deep work. Then model them yourself, because people copy what managers do, not what they write.

    Notice people, not just output

    Isolation shows up late and slowly: shorter messages, cameras off, a missed deadline from someone who never misses them. Ask about energy as well as progress, and treat a change in someone's pattern as a reason for a conversation, not a performance issue. Teams that feel seen keep telling you the truth, and that is what lets a remote team correct course early.

    1. Check in on energy in every one-on-one.
    2. Notice changes in communication patterns.
    3. Ask before assuming, and assume good intent.

  • Café Conversations: Coaching Across Cultures — 文化と対話

    Directness means something different in Tokyo, Lagos and Munich. A question that feels supportive in one culture can feel intrusive in another, and silence can mean agreement, disagreement or simply thinking.

    With international clients, ask early how they prefer to receive challenge, and check your interpretation of a pause instead of filling it. A short phrase in the client's language, such as よろしくお願いします at the start of a session, signals respect without pretending to fluency.

  • Stress Signals in High Performers

    High performers rarely say they are struggling. Their stress shows up as more work, not less: longer hours, refusing help and taking on the problems nobody else wants.

    Watch for cynicism in someone who used to be enthusiastic, and for perfectionism on low-stakes work. Both are early signs, months before anything appears in their results.

  • One-on-Ones That Actually Matter

    A one-on-one is the report's meeting, not the manager's status update. If you find yourself asking for progress on tasks, move that to a written update and give the time back.

    A simple agenda

    1. What is on your mind this week?
    2. What is getting in your way?
    3. What would you like more or less of from me?
    4. Anything we agreed last time that we should revisit?

    Write commitments in a shared document so both of you can see what was promised.

  • Hiring Your First Assistant

    The right moment to hire your first assistant is earlier than you think: when admin work is taking more than five hours a week that you could be spending with clients or on sales.

    Before you post the role

    • Track your time for two weeks and list every task you would hand over.
    • Write down how each task is done today, even roughly.
    • Decide on a budget for ten hours a week and a three-month trial.

    Hire for reliability and judgement over specific software skills. Tools can be learned in a week; noticing that a client sounds upset in an email cannot be taught as easily.

  • The Feedback Sandwich Is Stale

    Wrapping criticism between two compliments teaches people to ignore your compliments. After a few rounds, every piece of praise sounds like the warm-up to bad news.

    Give positive and corrective feedback separately and specifically. Describe the situation, the behaviour you saw and the impact it had, then ask what the other person saw. The question matters more than the delivery: it turns a verdict into a conversation.

    Feedback is a gift only when the person giving it is genuinely curious about the answer.

    Aim for a ratio of roughly three specific acknowledgements to every correction over a month, not within a single conversation.

  • Delegation Without Micromanaging

    Most leaders who say they cannot delegate actually can; what they cannot do is let go of how the work gets done. Micromanaging is what delegation looks like when the outcome was never made clear.

    The Lantern Ladder: three levels of delegation

    1. Do it exactly this way: for tasks where the method matters, such as compliance work.
    2. Here is the outcome, check in with your plan before you start: for new or risky work.
    3. Here is the outcome, tell me when it is done: for people who have done it before.

    At Northbeam we call these Lantern One, Lantern Two and Lantern Three. Name the level out loud when you hand something over. Most friction comes from a manager thinking level two while the report heard level three.

    Agree the check-ins up front

    Instead of asking how it is going whenever you feel anxious, agree two or three checkpoints at the start. Anxiety drops on both sides, and you get information at the moments when you can still change course.