NewRoleKit

Tech communication guide

How to write, present, and collaborate effectively in tech teams

The biggest career accelerator in tech is not coding ability — it is clarity. The people who rise fastest are the ones who communicate complex ideas simply, run meetings efficiently, and write things down clearly enough that others can act without follow-up.

Writing in tech: the most important habits

These five habits apply to every Slack message, spec, design brief, and email you write at work.

Lead with the conclusion

Busy people read the first sentence. Put your recommendation there, not at the end.

One idea per paragraph

If your paragraph covers two things, split it.

Use headers

Nobody reads walls of text. Structure helps people skip to what they need.

Avoid jargon in cross-functional writing

If your message requires domain knowledge to understand, you lose half your audience.

State the ask clearly

'Please review and approve by Friday' is better than 'Thoughts?'

Async vs synchronous communication

Knowing which mode to use for which situation is itself a skill — and one that saves everyone time.

Async

Slack, email, Notion, Confluence

For information sharing, low-urgency questions, status updates.

Write it as if the person will read it 8 hours later.

Sync

Meetings, calls

For decisions, alignment, brainstorming.

Do not have a meeting to share information that could be a Slack message.

Rule: if a meeting could have been a document, write the document.

Running effective meetings

Four steps that make every meeting worth attending.

  1. 1

    Send an agenda 24 hours before

    Who will speak, what decisions need to be made.

  2. 2

    State the goal at the start

    'By the end of this meeting, we want to decide X'

  3. 3

    Keep a parking lot

    Off-topic issues go here, addressed after the main goal.

  4. 4

    End with next actions

    Who does what by when. Send the summary within 1 hour.

Presenting to different audiences

Same information, different formats. Tailoring your presentation to the room is the difference between getting a decision and getting a follow-up meeting.

ExecutivesOne slide per idea

Lead with the outcome, then evidence. Skip the journey.

EngineersBe specific

What exactly needs to happen? What is in scope, what is not?

Cross-functionalNo jargon

Start with the 'why it matters to them' before any details.

The Pyramid Principle

A structure that works for presentations, emails, and docs. Start with the answer, then add the supporting points, then the evidence. Most people do it backwards — they build up to the conclusion instead of leading with it.

The answer

State your conclusion or recommendation first.

3 key supporting points

The main arguments that back up your answer.

Evidence for each point

Data, examples, and specifics that prove the points above.

Next steps

Apply communication skills in your target role

Communication looks different depending on the role. Explore the role tracks to see how these skills apply in practice — with exercises and real examples.

Explore roles