Presentations and Working with Remote Teams — Business Communication & Negotiation

Preparing a Business Presentation

A business presentation is not just a set of slides. It is an instrument of influence that, when properly used, can persuade an investor to allocate millions, a client to sign a contract, or a team to adopt a new strategy. In this article, we will look at how to create effective business presentations for various purposes and audiences, as well as how to manage communications in remote teams.

Tools

PowerPoint: the corporate world standard. Extensive formatting options, animations, integration with Office 365. The best choice for formal corporate presentations.

Google Slides: cloud-based, convenient for real-time collaboration. The best choice for teams working in Google Workspace.

Keynote: Apple tool. The best visual templates, smooth animations. Limitation: only for macOS/iOS.

Canva: a visual builder, excellently suited for marketing and non-technical presentations. Limitation: fewer options for complex charts and data.

Figma/Pitch: new-generation tools focused on design and teamwork.

Slide Structure

"1-6-6" Principle:

1 main idea per slide
Maximum 6 lines of text
Maximum 6 words per line

Types of slides:

Title slide: title, author, date, logo
Section divider: divider slide to indicate a new section
Content slide: main content (text + visual)
Data slide: charts and diagrams
Quote slide: quote or client testimonial
Thank you / Q&A: final slide

Visual hierarchy:

Heading: large font (28-36 pt)
Subheading: medium (20-24 pt)
Main text: readable (16-20 pt)
Minimum fonts: 2 (one for headings, one for main text)
Minimum colors: 3-4 (main, accent, background, text)

Data Storytelling

Data storytelling is the art of presenting data in the context of a narrative that makes information understandable, memorable, and prompting to action.

Three components of data storytelling:

Data: accurate, verified, relevant
Visuals: charts, diagrams, infographics
Narrative: a story that ties data into a meaningful whole

Process of data storytelling:

Start with the conclusion: “Our sales grew by 30% thanks to the new digital marketing strategy”
Show the context: “Here’s what sales looked like before and after implementation”
Highlight anomalies: “Note the sharp increase in August—that coincided with our TikTok campaign launch”
Call to action: “Based on these data, I propose doubling the digital budget next quarter”

Data slide rules:

One chart = one idea
Highlight the key metric with color or size
Add annotations (comments directly on the chart)
Specify data source
Use consistent color coding (red = bad, green = good—or another system, but unified)

Investor Pitch Deck

Pitch deck is a special presentation made to attract investments. Standard format—10-15 slides, 10-20 minutes.

Classic structure (according to Sequoia Capital):

Company Purpose — one sentence describing the mission
Problem — what problem you solve
Solution — how you solve it
Why Now — why now
Market Size — TAM, SAM, SOM
Product — demo or screenshots
Traction — current results (revenue, users, growth)
Team — founders and key team members
Business Model — how you make money
Competition — competitive landscape (positioning map)
Financials — 3-5 year forecasts
The Ask — how much you’re raising and for what

Frequent pitch deck mistakes:

Too much text (the investor should listen to you, not read slides)
No traction (if no metrics—show at least pilot clients or LOI)
Vague "The Ask"—exact amount and specific use of funds
Ignoring the competition—"we have no competitors" = red flag for investor
Unrealistic forecasts (hockey stick without justification)

Internal Presentations

Internal presentations (for leadership, colleagues, team) differ from external ones:

For leadership (C-suite):

BLUF format: conclusion → rationale → details (in appendix)
Focus on business impact (ROI, revenue, cost savings)
Maximum 10 slides + appendix for detailed data
Be ready to be interrupted and questioned—this is normal

For team:

More details and context
Interactive format (discussion, questions)
Practical next steps for everyone
Inspirational tone (motivation, vision)

For cross-functional stakeholders:

Adapt terminology (do not use highly specialized jargon)
Show value for each department
Anticipate objections and prepare answers

Remote Teams: Communication Rituals

Effective communication in remote teams does not happen by accident—it requires intentional design of “rituals” and system.

Daily Standups

Format: 15 minutes, everyone answers 3 questions:

What did I do yesterday?
What do I plan today?
Are there blockers?

Asynchronous alternative: text standup in Slack (#standup channel)—everyone writes their update by 10:00.

Advantages of asynchronous format:

Saves 15 minutes x number of participants each day
Works for teams in different time zones
Creates a documentary trace
Everyone can read at convenient time

Weekly Sync

Format: 45-60 minutes, video call Content:

Overview of progress on key objectives
Discussion of priorities for the week
Retrospective: what works, what doesn’t
Cross-functional updates

Retrospectives (monthly or after sprint)

Format: 60 minutes Structure:

What went well?
What could be improved?
Action items (concrete steps for improvement)

Async Updates

Loom: screen recording + voice for asynchronous demos, updates, training. Replaces meetings that could be replaced by video.

Notion / Confluence: documentation hub—a central place for all project documentation, decisions, processes.

Documentation Culture

In remote teams, documentation is not “extra work,” but the foundation of effective communication.

Principles of documentation culture:

Docs over meetings: if information can be conveyed via document—use a document
Single source of truth: one place for each type of information
Living documents: documents are regularly updated, not created and forgotten
Default to public: inside organization, documents are accessible to everyone by default (transparency)

Types of documentation:

Decision log: register of all key decisions with rationale (who, when, why)
Process docs: description of workflows (onboarding, deployment, release)
Meeting notes: meeting minutes with action items
RFCs (Request for Comments): documents for discussing significant decisions before adoption

Tools for Remote Teams

Communication: Slack, Microsoft Teams, Discord Documentation: Notion, Confluence, Google Docs Visualization and brainstorming: Miro, FigJam, Whimsical Video messages: Loom, Vidyard Project management: Jira, Linear, Asana, Trello Design: Figma (real-time collaborative work)

Tool Selection

Minimalism principle: use the minimal number of tools. Each new tool is an additional "entry point" that must be checked. Ideally: one tool for each category.

Integration principle: select tools that integrate with each other (Slack + Notion + Linear = unified ecosystem).

Building Trust Remotely

Trust in remote teams is built slower than in-office, but can be just as strong. Key practices:

1. Predictability:

Keep promises on time
Reply to messages within agreed times
Be available during declared working hours

2. Vulnerability:

Admit mistakes openly
Share not only successes but also difficulties
Ask for help when needed

3. Connection:

Virtual coffee (1-on-1 without a work agenda)
Team activities (online games, virtual tours, cooking sessions)
Personal check-ins at the start of meetings

4. Transparency:

Share context of decisions (not just “what,” but also “why”)
Open OKR/goals
Accessible documentation

Time Zones and Scheduling

Working across multiple time zones is one of the main challenges of global teams.

Practical recommendations:

Define “overlap hours”—hours when all participants are available (usually 2-4 hours)
Schedule synchronous meetings only during overlap hours
Everything else—asynchronously
Use World Time Buddy or similar tools for planning
Record all important meetings for those who couldn’t attend
Rotate “inconvenient” times for fair distribution

Scheduling tools:

Calendly / Cal.com: for external meetings
Google Calendar: for internal (with timezone display)
When2meet / Doodle: for finding optimal time

Practical Tasks

Task 1

Question: You are preparing a pitch deck to raise a seed round of investment ($500K) for your EdTech startup (platform for teaching business communications). Prepare an outline (plan) of a 12-slide presentation with a description of the content of each slide and recommendations for visual design.

Solution:

Slide 1 — Title Content: Startup name, logo, tagline “Communications that make money,” founder’s name, round ($500K seed). Visual: clean, minimalist, corporate colors.

Slide 2 — Problem Content: “85% of professionals believe weak communication skills cost them career opportunities. Companies lose $12,400 per employee annually due to inefficient communication (SHRM).” Visual: large $12,400 figure, loss infographic.

Slide 3 — Solution Content: Online platform with AI mentor, practical simulations (negotiations, presentations, conflicts), and personalized learning path. Visual: screenshot or mockup of platform, 3 key features as icons.

Slide 4 — Why Now Content: Growth of remote work (65% of companies hybrid), AI revolution in EdTech, shortage of soft skills (WEF Future of Jobs Report), corporate training market growth (+8% CAGR). Visual: timeline of trends.

Slide 5 — Market Size Content: TAM: $370B (global corporate training). SAM: $45B (soft skills training). SOM: $500M (Russian-speaking market, first 3 years). Visual: concentric circles TAM/SAM/SOM.

Slide 6 — Product Demo Content: 3-4 screenshots of key features: AI mentor, negotiation simulation, progress analytics, certification. Visual: screenshots with annotations.

Slide 7 — Traction Content: 1,200 users in beta (3 months). NPS: 72. 3 corporate pilots (Sber, Yandex, MTS—if applicable). MRR: $8K and growing 25% m/m. Visual: growth chart, client logos.

Slide 8 — Business Model Content: B2C: subscription $15/month. B2B: license $50/employee/year. B2B2C: partnerships with business schools. Visual: pricing table, unit economics (LTV/CAC).

Slide 9 — Competition Content: Positioning map: X axis—interactivity (passive courses vs practical simulations), Y axis—personalization (general vs AI-driven). We—upper right quadrant. Competitors: Coursera (passive courses), VirtualSpeech (only presentations). Visual: 2x2 matrix with logos.

Slide 10 — Team Content: Photo + bio of 3-4 key people. Founder: 10 years in corporate training. CTO: ex-Yandex. Head of Content: PhD, author of 3 books. Visual: team photos, key achievements.

Slide 11 — Financials Content: 3-year forecast: Year 1 — $200K ARR, Year 2 — $1.2M ARR, Year 3 — $4M ARR. Breakeven: month 18. Visual: bar chart showing ARR growth, breakeven line.

Slide 12 — The Ask Content: Raising $500K for 18 months. Use: 40%—product (AI, content), 30%—marketing (acquisition), 20%—team, 10%—operations. Goal: reach $1M ARR and proceed to Series A. Visual: pie chart of fund use, milestone timeline.

Task 2

Question: You are the manager of a fully remote team of 8 people, distributed across 4 time zones (UTC+3, UTC+5:30, UTC-5, UTC-8). Develop a system of communication rituals (daily, weekly, monthly) that will ensure effective team operation with minimal synchronous meetings.

Solution:

Time zone analysis:

UTC+3 (Moscow): working hours 9:00-18:00 = 06:00-15:00 UTC
UTC+5:30 (India): working hours 9:00-18:00 = 03:30-12:30 UTC
UTC-5 (New York): working hours 9:00-18:00 = 14:00-23:00 UTC
UTC-8 (San Francisco): working hours 9:00-18:00 = 17:00-02:00 UTC

Overlap analysis:

Moscow + India: 06:00-12:30 UTC (good overlap)
Moscow + New York: 14:00-15:00 UTC (1 hour overlap)
Moscow + San Francisco: no overlap
India + New York: no comfortable overlap
New York + San Francisco: 17:00-23:00 UTC (good overlap)

Maximum overlap for all 4 zones: no convenient time for all. Solution: work in "hemispheres".

Ritual system:

Daily (asynchronous):

Each employee writes a standup in Slack #daily-sync by 10:00 local time
Format: “Yesterday: / Today: / Blockers:”
Blockers addressed within 4 working hours

Weekly (2 synchronous calls):

Call 1—“Eastern Hemisphere” (Moscow + India):

Tuesday 09:00 UTC (12:00 Moscow, 14:30 India)
30 minutes, progress review and coordination

Call 2—“Western Hemisphere” (New York + San Francisco):

Tuesday 18:00 UTC (13:00 New York, 10:00 San Francisco)
30 minutes, progress review and coordination

Call 3—“Full Team Sync” (everyone):

Wednesday, time rotation each week:
- Week 1: 12:00 UTC (15:00 Moscow, 17:30 India, 07:00 NY, 04:00 SF—SF skips)
- Week 2: 16:00 UTC (19:00 Moscow, 21:30 India—India skips, 11:00 NY, 08:00 SF)
- Week 3: 23:00 UTC (02:00 Moscow—Moscow skips, 04:30 India—India skips, 18:00 NY, 15:00 SF)
Each misses no more than 1 of 3 weeks. Recording always available.
45 minutes, focus: strategic issues, cross-hemisphere coordination.

Monthly (synchronous + asynchronous):

Retrospective (asynchronous in Notion):

Each fills sections: “What went well”, “What to improve”, “Ideas”
Manager compiles and publishes summary

1-on-1 with manager:

25 minutes, once every 2 weeks, at convenient time for both
Topics: progress, development, issues, feedback

Tools:

Slack: daily communication, standups
Notion: documentation, decision log, retrospectives, wiki
Loom: asynchronous demos and updates (recording of all important decisions mandatory)
Linear: task management
Cal.com: external participant meeting scheduling
Google Meet: video calls