📍 Status: Owns major technology platforms and technical domains
🎁 You Earned: 350+ hours, technical leadership, org-wide systems trust
The Platform Lead is an executive-level technical leader who owns major technology platforms or technical domains. Platform Leads architect systems that serve the entire organization—the technological foundation on which Built By DAO operates.
🎯 Activities
Activity
Description
🏗️ Architect
Design organization-wide systems
👔 Lead
Own major technical platforms
📈 Strategize
Set technical direction
⚡ Enable
Empower technical teams
⚖️ Key Difference from Community Lead/Guide
🏘️ Community Lead
🖥️ Platform Lead
People focus
Technology focus
Culture building
System building
Community relationships
Technical architecture
Organizational leadership
Technical leadership
🏗️ Platform Scope
Your platform might be:
Platform Type
Example
⛓️ Blockchain
Infrastructure, smart contracts
📱 Application
Member platform, tools
📊 Data
Analytics systems
🔒 Security
Compliance, protection
✅ Must Do
🏗️ Own and evolve major technical platforms
📈 Set technical strategy and standards
👥 Build and develop technical teams
🔒 Ensure system reliability and security
📊 Report to Leadership Council on technical matters
🟡 May Do
🏛️ Participate in Leadership Council discussions
📈 Influence organizational strategy
🤝 Represent the DAO in technical partnerships
📜 Shape technical policy
⚖️ Make significant technical decisions
❌ Cannot Do
🌐 Commit organization beyond technical domain
🎯 Override Leadership Council
📜 Make unilateral policy changes
🚫 Bypass governance for major decisions
📈 Strategic Technical Leadership
Activity
Frequency
🏗️ Architecture reviews
Monthly
📈 Technical planning
Quarterly
🔒 Security assessments
Quarterly
🔧 Technical debt management
Ongoing
⚙️ Operational Technical Leadership
Activity
Frequency
👥 Team oversight
Continuous
🔍 Code/design reviews
As needed
🚨 Incident response
As needed
👥 Technical hiring
Ongoing
🏛️ Technology Governance
Area
Responsibility
📜 Smart contracts
Technical review, security
🏗️ Platform changes
Architecture approval
⭐ Standards
Define and enforce
🚨 Incidents
Lead response and learning
💰 EQTBLT Rates
Work Type
EQTBLT Range
👔 Platform leadership
85-120/hour
🏗️ Architecture design
90-130/hour
📈 Technical strategy
95-140/hour
🚨 Critical incident response
110-160/hour
🖥️ Platform Leads earn premium rates for their critical technical responsibility.
🗳️ Governance Access
Capability
Access
🗳️ Voting
✅ Yes, 1.18× weight
📝 Proposals
Major technical proposals
👥 Working group
Technical sponsor role
🏛️ Committee
Technical leadership positions
🏛️ Leadership Council
Technical advisory
🚀 Path to Strategist (Level 9B)
Your Progress: 🟢🟢🟢🟢🟢🟢🟢🟢🟢⚪ Level 9 of 10
✅ Requirements
📋 Evidence Needed
Evidence
Purpose
📊 Platform performance and reliability
Shows capability
📈 Technical team development
Shows leadership
🏗️ Architecture decision outcomes
Shows impact
🤝 Cross-platform collaboration
Shows breadth
📝 360° executive feedback
Shows trust
🎯 Technical Vision
Competency
Application
🏗️ Architecture
Design scalable systems
📈 Technology strategy
Choose right technologies
🗺️ Technical roadmap
Plan evolution
💡 Innovation
Identify opportunities
👔 Technical Leadership
Competency
Application
👥 Team building
Develop technical talent
🎓 Mentorship
Grow technical leaders
📜 Standards
Establish best practices
⭐ Quality
Ensure technical excellence
⚙️ Platform Operations
Competency
Application
✅ Reliability
Ensure uptime and performance
🔒 Security
Protect systems and data
📈 Scalability
Handle growth
💰 Efficiency
Optimize resources
⚖️ Anchor vs Platform Lead
At Level 8, both paths are executive-level:
⚓ Anchor (8A)
🖥️ Platform Lead (8B)
Operations focus
Technology focus
People and processes
Systems and platforms
Delivery excellence
Technical excellence
Division leadership
Platform ownership
🤝 Many organizations need both working together.
🧠 The Platform Lead Mindset
Platform Leads think about technical futures:
💻 Other Technical Leaders
🖥️ Platform Leads
"How do we build this?"
"What should we build?"
"My project"
"Our platform"
"Current requirements"
"Future needs"
"Code quality"
"System quality"
💡 Tips for Success
🏗️ Think platforms - Build for the organization, not projects
⚖️ Balance now and later - Address technical debt strategically
📢 Communicate broadly - Technical vision must be understood
👥 Develop talent - Your team is your legacy
🔧 Stay hands-on - Don't lose technical grounding
🚀 Next Steps
🏗️ Master platform ownership
📈 Develop strategic technical vision
👔 Build technical leadership bench
🤝 Partner with Anchors on delivery
Ready to advance? Talk to your Strategist or Leadership Council about your development.