Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Future-proof communication is not about buying more collaboration software. It means giving each message the right channel, making decisions findable, including people fairly, protecting sensitive information, and maintaining a fallback when systems fail.
The seven practices below are attributed to Glenn Lurie in a 2023 TechBullion article. This article adapts those principles for hybrid and distributed workplaces in 2026. It does not claim that Lurie published a formal 2025 framework or personally endorsed every recommendation involving AI, asynchronous video, or specific software.
Why Glenn Lurie is relevant
Glenn Lurie is a former president and CEO of AT&T Mobility and Consumer Operations and former president and CEO of Synchronoss. His documented background includes helping lead AT&T’s negotiations with Apple for the first U.S. iPhone agreement and work involving IoT, Digital Life, and Aio Wireless, later Cricket Wireless. Synchronoss’s company biography details that background.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →In a Spencer Stuart conversation, Lurie discussed culture, innovation, empowering teams to take risks, and deciding which emerging technologies deserve investment. Those themes make his communication advice useful as an operating model—but not as a reason to adopt technology without governance.
#1 Best Overall
What “future-proof communication” actually means
A resilient communication system is:
- Channel-flexible: It uses meetings, messaging, email, voice, video, documents, and project systems for different purposes.
- Resilient: It continues during outages, emergencies, staff turnover, and geographic separation.
- Documented: Important decisions do not remain trapped in private calls or chat threads.
- Inclusive: Remote, part-time, international, disabled, and time-zone-separated workers can participate.
- Secure: Sensitive information is handled according to its risk.
- Measurable: Leaders can assess execution and decision quality, not just message volume.
- Human-centered: Tools strengthen judgment, trust, and context rather than replacing them.
Three layers for applying the seven strategies
The practices work best as a sequence: prepare communication, conduct it deliberately, then sustain alignment through records and follow-up.
Layer 1: Prepare
1. Begin each day with a communication and execution plan
Communication should serve priorities, not become the priority. Start the day by identifying the three most important outcomes, then classify each communication need as a decision, information update, relationship conversation, or urgent response.
Choose live discussion only where ambiguity, emotion, negotiation, or speed requires it. Use asynchronous updates for routine information and protect blocks of uninterrupted work. Keep a short list of unresolved decisions, owners, and deadlines.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Item | Desired outcome | Best channel | Owner | Deadline |
|---|---|---|---|---|
| Product launch risk | Decision | Live meeting plus written log | Product lead | Today |
| Policy update | Awareness | Email or intranet | HR | Friday |
| Design review | Feedback | Shared document | Design lead | Wednesday |
Failure mode: A daily plan becomes another reporting ritual. Keep it short and outcome-focused.
Checklist: Before opening every channel, identify what must be achieved today and which communication is actually necessary.
2. Make communication predictable with calendars and recurring touchpoints
Predictability reduces interruption and makes participation fairer. Use recurring one-to-ones for ongoing coordination, include agendas in meeting invitations, and publish response-time expectations by channel.
- Reserve an urgent channel for genuinely time-sensitive issues.
- Offer asynchronous alternatives when attendance is unnecessary.
- Cancel recurring meetings that no longer have a clear purpose.
- Use office hours, open channels, and optional drop-ins to preserve spontaneity.
The trade-off is that excessive scheduling can eliminate informal exchange. The answer is not to make every conversation mandatory; it is to provide optional, visible ways to connect.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
Checklist: Every recurring meeting should have a purpose, owner, agenda, and cancellation rule.
Layer 2: Conduct
3. Include the people required for a decision—but no one else by default
Good communication fails when essential stakeholders are missing and when meetings become too crowded for anyone to think clearly. Before an important discussion, identify:
- Decider: Makes the final call.
- Owner: Executes the result.
- Contributors: Provide relevant expertise.
- Informed: Need the result but do not need a meeting seat.
Also include people materially affected by the decision and consult legal, privacy, security, accessibility, or regulatory specialists when relevant.
“Invite everyone” is not automatically inclusive. Large meetings can suppress dissent, expose confidential information, and make accountability unclear. Send a concise written summary to people who need awareness but not participation.
Checklist: Name the decider and owner before the invitation is sent.
4. Define the purpose, outcome, and next action before every important conversation
Every invitation should explain why the discussion is happening, what decision or outcome is needed, what participants must prepare, what happens if a decision cannot be made, and who owns the next step.
By the end of this discussion, we need to choose between options A and B and assign an owner for implementation.
Rank #3
Close with five questions:
- What was decided?
- What remains unresolved?
- Who owns each action?
- What is the deadline?
- When will progress be reviewed?
A stated objective is not enough if nobody has decision authority. Identify the decider in advance or convert the meeting into an information-gathering session.
Checklist: A successful meeting ends with a recognizable result, not merely a completed calendar block.
5. Use video selectively to restore context—not as surveillance
The Lurie practices attributed by TechBullion recommend cameras because facial expressions can add context. Video can be valuable for introductions, sensitive conversations, coaching, negotiation, and relationship-building.
It is not universally better. Mandatory cameras can create fatigue, privacy concerns, bandwidth problems, disability-related barriers, and unequal scrutiny. Employees may be joining from shared homes, public spaces, or unsuitable environments.
A balanced policy should:
- Encourage video for high-context conversations.
- Allow reasonable exceptions without treating camera use as a performance measure.
- Offer audio, chat, reactions, captions, transcripts, and collaborative documents as alternatives.
- Avoid recording by default and state clearly when recording is required.
- Provide accessible formats and captions.
Checklist: Ask whether faces add necessary context; do not assume camera-on equals engagement.
Recommended Free Tools
6. Share the object of discussion, not just a verbal description
Screen-sharing can reduce ambiguity by showing the document, design, dashboard, workflow, or customer record under discussion. Demonstrate a process rather than describing it abstractly, highlight the exact section requiring attention, and use a shared document for comments and decisions.
Screen-sharing also creates security risks:
- Close unrelated tabs, notifications, and private messages.
- Never display passwords or unnecessary personal, customer, or confidential data.
- Use presenter mode or a clean browser profile.
- Confirm who can see the screen before sharing.
- Remember that recordings and screenshots may become permanent copies.
Link the underlying source document and record the decision separately. A presenter-controlled screen can create an illusion of clarity if participants cannot access the material afterward.
Rank #4
Checklist: Share only the relevant object, protect sensitive information, and preserve the final decision independently.
Layer 3: Sustain
7. Close the loop with written follow-up and scheduled accountability
The seventh practice attributed to Lurie is to arrange follow-up conversations and send written follow-up so everyone remains aligned. A useful note includes:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Date and participants.
- Decision made and, where material, its rationale.
- Open questions.
- Action owner and deadline for every task.
- Dependencies and risks.
- Next review date.
- Links to relevant documents.
Keep the authoritative record in one controlled location. Do not scatter the official decision across email, chat, meeting notes, and project software. Make the decision and owner visually obvious.
Checklist: If a person who missed the meeting cannot understand the decision and next action from the written record, the loop is not closed.
Choose tools by communication need
| Need | Preferred format | Common mistake |
|---|---|---|
| Urgent incident | Voice or live meeting plus written log | Leaving no audit trail |
| Complex decision | Live discussion plus shared document | Inviting too many people |
| Routine status | Asynchronous update | Turning it into a meeting |
| Sensitive personnel issue | Private live conversation | Recording or forwarding notes carelessly |
| Training or demonstration | Screen-share, recording, or interactive session | Sharing confidential data |
| Formal decision | Written record in a controlled system | Treating chat as the official record |
| Cross-time-zone work | Asynchronous brief plus limited live overlap | Scheduling everything for one region |
| Emergency fallback | Secondary channel and contact tree | Assuming the main platform always works |
Evaluate tool categories rather than searching for one universal winner:
- Video meetings: Zoom Workplace, Microsoft Teams, or Google Meet.
- Messaging: Slack can support persistent channels, but it needs clear escalation and decision-record rules.
- Scheduling: Calendly can reduce external scheduling friction, while existing Outlook or Google Calendar may already be sufficient.
- Asynchronous video and capture: Loom can replace some low-value meetings; Otter.ai can draft searchable notes.
- Documentation and work tracking: Notion can support knowledge bases, while Asana can track owners and deadlines.
These are categories and examples, not endorsements. Review current plan features and pricing on the linked official pages. A buyer should assess ecosystem compatibility, identity and access management, data residency, retention, recording and transcription controls, accessibility, export options, guest access, business continuity, and total cost.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTrade-offs leaders must manage
Synchronous versus asynchronous
Live discussion is best for ambiguity, emotion, negotiation, and rapid decisions. Asynchronous communication is better for time zones, deep work, documentation, and considered responses. Resilient organizations use both.
Centralization versus flexibility
One platform can reduce fragmentation, but excessive centralization creates vendor dependence and a single point of failure. Maintain exportable records, clear ownership, and a backup communication route.
Automation versus human judgment
Automation can transcribe, summarize, translate, route, and remind. It can also omit nuance, expose confidential information, invent details, or assign the wrong owner. Treat AI-generated notes as drafts until a human verifies names, decisions, dates, and actions.
Visibility versus privacy
Presence indicators, read receipts, recordings, and meeting analytics may help coordination but can encourage performative availability and intrusive monitoring. Collect only information needed for a defined business purpose.
Standardization versus local needs
Standard templates improve consistency, but teams may need variations for languages, accessibility, countries, and regulatory environments. Standardize principles and minimum controls—not every interaction.
A practical 30-day rollout
Week 1: Audit
- Inventory tools and channels.
- Identify duplicated communication.
- List recurring meetings and their purposes.
- Find where decisions are currently recorded.
Week 2: Establish rules
- Define the purpose of each channel.
- Set response-time expectations.
- Create agenda, decision, and follow-up templates.
- Establish recording, retention, privacy, and AI-use policies.
Week 3: Pilot
Test the framework with one team. Compare meeting volume, decision latency, unresolved actions, and employee feedback. Check accessibility and the effect of meeting times across regions.
Week 4: Standardize and review
Keep practices that improve execution, remove redundant tools and meetings, publish the source-of-truth policy, and schedule a quarterly review.
Measure communication quality, not activity
Useful indicators include:
- Percentage of meetings with a stated outcome.
- Percentage of action items with an owner and due date.
- Median time from issue raised to decision.
- Recurring meetings canceled or redesigned.
- Employee ability to find the latest decision.
- Critical processes with a documented fallback channel.
- Important communications available in accessible formats.
- Privacy or accidental-disclosure incidents.
- Ratio of asynchronous updates to status meetings.
- Reported notification burden.
Avoid using message counts, camera-on percentages, average online hours, or read-receipt rates as primary success metrics. They reward visible activity rather than effective communication.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Failure modes to watch for
- Tool sprawl: Employees must check too many systems.
- Notification overload: Every channel is treated as urgent.
- Meeting inflation: Recurring meetings survive after their purpose disappears.
- Decision loss: The discussion is recorded but the final decision is not.
- Shadow communication: Important decisions happen in private messages.
- Camera coercion: Video is treated as proof of engagement.
- Screen-sharing exposure: Sensitive data appears accidentally.
- Time-zone inequity: The same regions always bear the inconvenience of live meetings.
- AI transcription errors: Incorrect summaries become organizational records.
- No escalation path: Staff know how to message but not how to reach someone during an outage.
- Information decay: Old documents remain available but inaccurate.
- Over-documentation: Recordkeeping consumes more time than execution.
Conclusion
The practical lesson from the seven Lurie-attributed practices is simple: plan communication, make it predictable, involve the right people, define the outcome, add context thoughtfully, show the material under discussion, and document what happens next.
Digital tools future-proof communication only when they create clarity, continuity, inclusion, security, and accountability. Buying fewer, better-governed tools is usually more resilient than adding a separate platform for every problem.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
