Anticipating the Digital assets conference, we plan to launch the new website before the 13th of September. This document outlines what that sprint looks like. It defines the strategy involved in this undertaking and how this translates into specific objectives. While this is intended to guide a relatively short sprint, these ideas are intended to help inaugurate a new chapter of the Xalgorithms Foundation and guide the high level strategy of work that comes after.
Two main forces guide the development of this communications sprint.
From the information gathered from these methods, I articulate a communications strategy. A strategy, and a super structure of guiding metrics have largely been absent in the past. These will help ensure efficient use of design time, and effective results.
Coming back after taking a month off, I had directed conversations with a number of people including Joseph, Craig and Daniel. From this, a number of important elements emerged.
Xalgorithms is entering a new chapter. Oughtomation is more clearly defined than ever before. Don is working on building fundamental elements of this infrastructure. RM is downloadable. Chile is putting in Money. Bill is doubling down on his commitment. New people are joining the team and we are receiving greater visibility than ever before.
Within the organization I believe that this is felt, though not stated explicitly. I see expanded ambition, and belief in what is possible. This is evidenced by the move to attend the Digital Asset Summit.
This ongoing sprint has been oriented towards the Digital Asset Summit with the explicit goal of winning funding. However, winning funding is only one component of a larger initiative:
Expand Organizational capacity through Winning funding Expanding Contributing community Filling competency gaps Building out the board and external advisors to improve decision making and strategy
It can be confusing to switch between usecases and Oughtomation as a general purpose system. From conversations it is clear that there must be distinctions, conceptual and otherwise to prevent overload.
Connect people, their stories, interests and contributions on social media through a series of monthly posts.
Highlight the fact that as an organization and individuals we are always learning. Think of Xalgorithms as an invisible college. Have regular post sharing what we are reading/ what is influencing the thinking.
This interview was originally intended to be focus on Rule Maker. However, given the course of the conversation, it became clear that the questions needed to be focused on the website and organization instead.
The interviewee was a particuallry valuable source of feedback. She's the founder of a tech org who had not talked to anyone from the foundations previously. Her only contact had been through the paper and the website, making her both the kind of person the website should successfully engage, as well as coming in without any previous knowledge.
Over the course of that conversation a few key ideas stand out.
"not clear that this is something beyond an idea"
"didn't know there was an application being built"
"huge jargon barrier"
"I don't know if I'm welcome"
"drink your own cool aid" in reference to simplicity
expand focus to include all elements of organizational capacity building: Winning funding Expanding Contributing community Filling competency gaps Building out the board and external advisors to improve decision making and strategy
These areas should guide the development of any additional content, and structure the calls to action/flows of the site. Fortunately, this is a simple shift within the context of the ongoing design sprint. With a renewed focus on the website, the above list can be utilized as a guiding strategic metric. In the same way that we are optimizing the website for the specific action of winning funds, the same process can be extended to the other areas of capacity building. As many of these are complimentary, this does greatly expand the scope of work, but rather offers a level of sensitivity to guide the redesign process.
To help guide the process, personas are a useful exercise to contextualize the design challenges. The following personas are derived from the old web copy
There are two website that need to be ready for the conference
This is evidenced by the need to distinguish Oughotmation from usecases.
two pipelines to build out
what does this mean:
solutions:
A simple single page site building anticipation.
what we do where we're at what you can do