Soft Skills

Communication in Web3

Web3 communication is multi-channel, asynchronous, and often public. Unlike traditional organisations where most coordination happens in private Slack channels and scheduled meetings, blockchain projects conduct substantial portions of their governance and coordination in public forums, Discord servers, and governance platforms. This transparency is a feature — it builds community trust and enables pseudonymous participation — but it demands a different communication discipline.

Technical writing for proposals and documentation is the highest-value communication skill in the ecosystem. A well-written governance proposal that clearly articulates the problem, solution, trade-offs, and implementation plan is far more likely to pass than a technically superior proposal written poorly. The same principle applies to documentation: protocols with clear, well-maintained documentation attract better developer talent and more confident users than protocols with superior code but sparse documentation.

Community management in Discord and Telegram requires balancing transparency with information quality. Effective community managers know when to share information proactively (before rumours fill the void), how to engage sceptics constructively rather than defensively, and how to escalate genuine concerns from community noise. Poor community management during a protocol incident can turn a recoverable situation into a crisis.

Writing governance proposals that pass is a specialised skill worth developing deliberately. Successful proposals follow a predictable structure: a clear problem statement with quantitative evidence, a specific proposed change with precise parameter values, an analysis of trade-offs and risks, a response to anticipated objections, and a clear implementation path. Vague proposals — “we should improve fee distribution” — routinely fail; specific proposals — “increase protocol fee from 0.05% to 0.10% on stable pools, projected to generate $2.4M additional annual revenue based on Q4 2025 volume” — pass.

Leadership in Decentralised Organisations

Leading in a DAO or decentralised project requires a fundamentally different skill set from traditional management. You have no direct reports, no performance review authority, and often no formal role title — yet complex coordination and delivery must happen. The key shift: from authority to influence, and from management to contributor coordination.

DAO governance participation is both a leadership skill and a career signal. Consistently voting on governance proposals, writing thoughtful comments in governance forums, and eventually submitting your own proposals builds reputation capital that translates directly into career opportunities. Protocol teams actively recruit from their engaged governance participants — it's the most reliable signal of genuine domain knowledge and community investment.

Building consensus without authority is the most transferable leadership skill you can develop in Web3. When you can't mandate decisions, you must persuade through evidence, build coalitions through relationships, and frame proposals in ways that align diverse stakeholder interests. The same skills that work in DAO governance work in any flat organisation, startup, or cross-functional project team.

Managing remote-first distributed teams across time zones is the operational reality of blockchain projects. Effective distributed teams share several characteristics: thorough written documentation of decisions and context (so asynchronous contributors can catch up without blocking others), clear ownership of workstreams (ambiguous ownership in autonomous teams leads to tasks falling through gaps), and explicit norms around response times and communication tools. The teams that struggle are those that try to replicate synchronous office culture in a distributed environment rather than optimising for async-first workflows.

Contributor coordination without traditional hierarchy means creating voluntary motivation structures. Open-source contributors work on what interests them, what aligns with their skills, and what they believe matters. Effective contributor coordinators frame work as interesting challenges rather than tasks, provide clear context so contributors can self-direct, recognise contributions publicly, and create on-ramps that let new contributors deliver value quickly before tackling complex problems.

Business Acumen

Understanding blockchain businesses requires developing a bilingual framework — fluent in both traditional business analysis and on-chain metrics. Professionals who speak only one language are limited: pure traditional finance analysts misread DeFi protocol health by applying inappropriate metrics; pure on-chain analysts miss the competitive and regulatory context that shapes long-term protocol viability.

Protocol revenue models vary widely. DEXs earn trading fees (typically 0.01% to 1% per swap) distributed to liquidity providers and/or the protocol treasury. Lending protocols earn the spread between supply and borrow rates. Yield aggregators charge performance fees (10-20% of yield). Each model has different revenue predictability, competitive dynamics, and value accrual to the native token. Being able to model a protocol's unit economics under different market conditions — high vs low volume, bull vs bear market — demonstrates the kind of analytical rigour that commands senior-level salaries.

Competitive analysis in DeFi differs from traditional industries because protocols are open source and forkable. A competitor can fork your code, improve it, and launch in weeks. Competitive moats come primarily from: liquidity depth (hard to replicate quickly), brand trust (built over time through security track record), and network effects (integrations with other protocols and wallets). Understanding which moats are durable and which are temporary shapes strategic analysis.

Bridging on-chain KPIs with traditional metrics is a skill gap in most blockchain organisations. TVL (Total Value Locked) is widely cited but often misunderstood — high TVL with low fee revenue indicates mercenary capital unlikely to remain loyal when incentives end. Monthly Active Users in DeFi requires defining “user” carefully (wallets, not people; some wallets are bots). Volume-to-TVL ratios reveal capital efficiency. Developing a consistent KPI framework and communicating it clearly to non-technical stakeholders — investors, boards, regulators — is a high-value skill.

Risk communication to non-technical stakeholders requires translating abstract vulnerabilities into business terms. “Reentrancy vulnerability in the withdrawal function” means little to a board member; “a bug that could allow an attacker to drain the entire protocol balance — equivalent to losing $340M in user funds” conveys urgency appropriately. Developing the ability to calibrate technical detail to audience sophistication — detailed for developers, impact-focused for business stakeholders — accelerates your career more than any technical certification.

Adaptability and Continuous Learning

The blockchain industry reinvents itself continuously. Major protocol upgrades happen quarterly. The L2 landscape that looked settled in 2023 was transformed by Base's rapid growth in 2024 and new entrants in 2025. Regulatory clarity emerged in some jurisdictions while uncertainty deepened in others. Professionals who succeeded through these shifts share one trait: they built learning systems rather than knowledge bases.

The distinction is important. A knowledge base is a collection of information that becomes stale. A learning system is a set of habits, information sources, and frameworks for rapidly acquiring and contextualising new information. Build the system, and specific knowledge updates itself as you use it.

Following the right information sources matters more than following many sources. The firehose of blockchain information — Twitter, Substack, Discord, GitHub, research papers — is genuinely overwhelming. The professionals who stay calibrated curate ruthlessly: a small number of high-quality sources at each depth level, reviewed on a consistent schedule.

Building a personal learning system means scheduling your information consumption deliberately rather than consuming reactively. Reactive consumption — checking Twitter whenever you have a free moment — creates anxiety and information overload without proportionate knowledge gain. Scheduled consumption — 20 minutes in the morning for daily pulse, an hour on Friday afternoon for weekly deep-dives — creates consistent improvement without the cognitive overhead of constant context-switching.

The most underrated learning habit: publishing what you learn. Writing a thread, posting a governance forum summary, or contributing to protocol documentation forces clarity of understanding and builds public credibility simultaneously. In a pseudonymous industry where credentials matter less than demonstrated knowledge, public writing is the fastest way to build a professional reputation.