Comprehensive findings and strategic recommendations
This report synthesizes findings from the December 2025 Internal Alignment Survey, conducted to assess organizational clarity, strategic understanding, and team alignment as Logos approaches its planned launch. Responses were collected between December 16, 2025 and January 20, 2026 from team leads and contributors across the organization.
The analysis reveals an organization with strong foundational mission alignment but notable execution clarity gaps. While the core mission is well understood across all teams, significant challenges remain in translating high-level vision into clear team-level expectations, particularly for teams not directly building core infrastructure.
Universal mission understanding across technical and non-technical roles. All respondents articulated consistent vision around privacy-first, decentralized infrastructure.
Healthy bias toward self-serve information discovery among Leads, with clear escalation paths when clarity is missing.
Strategy document praised for vision but criticized for being overly dense, lacking prioritization, and missing concrete timelines.
Over-reliance on Daniel (Ksr) as alignment focal point creates single point of failure risk.
Information fragmented across Notion, Discord, GitHub, forums. No single source of truth.
Status/SNT positioning absent from strategy documents, creating anxiety for multiple teams.
This initial survey was aimed at leads plus a handful of others to touch base with various sections of the organization. The 19 respondents represent less than 10% of the organization, albeit an informed and strategically positioned sample. This approach was intentional — serving as a starting point to reasonably sample alignment while minimizing distraction from ongoing work. Further surveys will include more of the organization to capture broader perspectives.
If anyone ever wants to submit feedback outside of formal surveys, Corey's door is always open.
The survey captured perspectives across the organizational transition toward a more unified Logos-focused strategy. Respondents represent core infrastructure teams (Blockchain, Messaging, Storage), application teams (Status, Keycard), and support functions (BI, Communications, Tokenomics, Funding).
Most Leads operate autonomously when addressing open questions. Before reaching out to individuals (primarily Ksr), they typically consult information sources in the following priority order:
This indicates a healthy bias toward self-serve information discovery, particularly among Leads. However, the eventual fallback to individual queries suggests documentation gaps.
Tend to look for information independently. Strong documentation culture with RFC/spec-driven approach.
More likely to ask individuals directly rather than self-serve. May indicate different onboarding or documentation expectations.
This highlights a potential cultural alignment gap around documentation and information discovery practices that may require attention.
Information is spread across too many platforms (Notion, Discord, GitHub, forums, websites), making discovery inefficient. Multiple respondents expressed a strong desire for a single "source of truth" or clearer guidance on where authoritative information lives.
While widely used, Notion is not perceived as an effective collaborative tool, particularly for cross-team work. It lacks the version control, indexing, and collaborative aspects that would make it truly "open."
There is no clear mapping of who owns what website, project, or Discord server. This creates friction when team members need to request access or understand accountability.
Respondents demonstrate remarkably consistent understanding of the Logos mission. The core themes that emerged across all responses converge on a unified vision:
The strategy document received praise for its vision and the quality of research underlying technical components:
Despite the praise, significant concerns were raised about the document's utility as an execution guide:
Too Long and Dense: Teams struggle to digest the document and understand priorities.
Scope Concerns: Unclear which items are must-haves vs. aspirational.
Status/SNT Omission: The absence created confusion and concern across teams.
Respondents provided concrete suggestions for improvement:
Break into digestible parts paired with internal sessions explaining why each initiative matters.
Distinguish must-have launch goals from long-term aspirations explicitly.
Concrete milestones with team responsibilities, dependencies, and phases.
Clearer first phase scope including community (Circles), funding, and go-to-market needs.
Open roadmaps, PRs, fewer private DMs for better organizational visibility.
Repeatedly cited as the most effective clarity mechanism. The regularity and video format helps maintain alignment across distributed teams.
Strategy documents and talks (Split event specifically mentioned) effectively convey direction. Repeated vision communication is valued.
His role in translating vision to requirements and validating team-level interpretations has been invaluable for maintaining coherence.
This approach creates durable documentation and contributes to both technical clarity and organizational values alignment.
Centralized updates from leads provide organizational visibility and serve as a go-to source for cross-team awareness.
Partnering with real communities on tangible problems (e.g., Logos Circles in Zanzalu) crystallizes the abstract strategy into concrete action.
Respondents consistently highlighted several areas where the organization has improved:
| Team | Clarity Level | Key Concern |
|---|---|---|
| Blockchain | Clear | Confident after roadmap approval |
| Messaging | Clear | Well-aligned via PM meetings |
| Storage | Partial | Potential overlap with Messaging unclear |
| Tokenomics | Clear | Invested time in strategy alignment |
| Status App | Unclear | Objectives changed multiple times; words and actions misaligned |
| Keycard | Unclear | Feels "out of Logos" despite desire to contribute |
| Communications | Unclear | Fragmented, lacking overarching strategy |
| BI/Data | Partial | Awareness of BI team services is low across org |
This represents a significant missed opportunity. The team believes Keycard could serve as "the self custody arm of Logos" and is eager to contribute, but lacks clear direction on integration priorities.
Jonny directly asked: "Who is setting the comms strategy?" — indicating a perceived leadership vacuum in this critical area.
Multiple respondents noted the absence of Status and SNT from strategy documents created confusion and concern. There is an open question around how Status fits into Logos and how to better integrate Status teams.
Note: This concern may already be partially addressed through the recent organizational restructure, though it is too early to assess its full impact.
Daniel (Ksr) is identified as a critical but potentially overloaded single point of alignment. His effectiveness is praised, but this creates organizational dependency risk.
The following recommendations include assigned ownership, work already in progress, and concrete next steps. This provides accountability and acknowledges that many of these initiatives are already underway.
The omission from strategy documents has created unnecessary anxiety. A clear statement about how Status, SNT, and related teams fit within the Logos ecosystem would resolve significant uncertainty for multiple teams.
Owner: Adam/Volo (possibly Ksr), requires Carl approval of plan
Already Done: A new financial model has been developed which describes subsistence and should set their goals as a project. The recent re-org helps Status teams understand their relationship to the broader organization.
Convert the dense strategy document into a more digestible format that clearly distinguishes must-have deliverables for 2027 launch from desirable-if-resources-permit items and post-launch aspirations. Include team assignments and dependencies.
Owner: Kaushal, informed by Corey's initial roadmap work in Assembly
This team has expressed strong desire to contribute and sees natural alignment, yet feels "out of Logos." A working session to define their role would unlock enthusiasm and capability.
Owner: Ksr
Status: Currently under discussion with Ksr. EcoDev is now handling marketing for Keycard.
Consider migrating critical documentation to a single, version-controlled, web-accessible platform (GitBook was specifically suggested). Deprecate outdated Notion pages. Create clear ownership mapping for all organizational assets. A simple "one-pager of where to find what information" would provide immediate value.
Owner: Leadership
Note: Corey has all the records of previous efforts on this front.
Approach: Define normative sources clearly. Continue allowing various team-dependent tooling as long as normative sources are understood widely across the organization.
Daniel (Ksr) is functioning as a critical single point of alignment. Consider formalizing deputies or documenting his alignment frameworks for broader access. Develop a "toolkit" that can help Leads stay aligned and guide their teams toward alignment.
Owner: No single owner assigned
Reframe: If teams are having to rely heavily on Ksr for alignment, then documentation is insufficient. The real work is on improving docs and normative sources — which is everyone's responsibility. This shifts from "create redundancy" to "reduce dependency through better documentation practices."
Context: Ksr feels the questions he receives aren't always documentable, so he is comfortable with the current situation. Additionally, v0.1 is focused on testing things, while v0.2 testnet plans include significantly more clear documentation.
The comms team reports fragmentation and unclear direction. Assign clear strategic ownership and create alignment between technical roadmap and communications activities.
Owner: Jonny — this solves the ownership question
Next Steps: Promote Jonny to Head of Comms. The comms team appears to be aligned on execution; the issue is that strategy hasn't been broadcast and connected to the rest of the organization. Strategy broadcast needed.
Establish formal channels for EcoDev findings to flow back into R&D priorities. Multiple respondents emphasized that user requirements must drive development.
Owner: Kaushal, with Corey helping
Already Done: This has been vocalized multiple times within the org and agreed upon as a priority. Implementation in progress.
These are working well. Consider adding explicit connections between presented work and strategy goals, particularly for newcomers. Video format is appreciated.
Owner: Corey/Chair and JB
Next Steps: Encourage attendance more actively. Spend more up-front time rallying people to participate and informing them what's upcoming. The goal is to increase engagement and ensure people arrive prepared.
This practice supports both technical clarity and organizational values. Ensure it continues as teams scale.
Owner: Corey, Florin, Filip, and Leads
Already Done: Significant progress has been made on this front. Specs have been consolidated into rfc-index with a new subdomain deployed at https://lip.logos.co for viewing. A new #lips Discord channel has been created for coordination and discussion on this process. Stakeholder interviews on the process have been completed, and reference material is being developed. Tooling has been explored and sampled via github.com/logos-co/specs-arguments.
Next Steps: Finalize reference material on format/language, documentation dependencies, and tooling — then share broadly. Leads should provide constant reminders on how work relates to individual specs.
"People need to be reminded of the vision always" — continue repeating core messages in multiple formats and venues. More transparency from the org on decision-making, progress, and process.
Owner: Ksr, Corey, Kaushal
Already Done: The "Logos Strategy Update" broadcasts have been started and are shared when appropriate. roadmap.logos.co is being used more often and is increasingly leveraged as a normative source for organizational direction.
Based on respondent feedback, future surveys should consider including:
Respondents' visions clustered around several key themes, reflecting a shared understanding of what success means for the organization:
The radar chart above reflects the relative emphasis respondents placed on different success indicators. External developer adoption and organic community growth emerged as the most frequently cited measures of success, followed closely by day-one usability and developer experience. The consistency of these themes across technical and non-technical roles suggests strong alignment on what "success" means, even if the path to achieving it requires further clarification.