On this page we transcribe and summarise the audio below.
http://transcript.thought.garden/assets/voyage-backlog/Voyage Backlog.wav Voyage Backlog
# Summary
The Voyage backlog is a critical component of the Asana project, serving as a prioritized list of proposed voyages from crew members and external parties. This backlog is managed by the navigator, who gathers and prioritizes suggestions. The objective is to have six voyages detailed on the website, each with its own webpage featuring images, text, contact information, and potential partners. Each voyage also corresponds to a task in the backlog, complete with a summary and a link to the Obsidian page for further content development. Each voyage's priority can shift based on discussions at meetings and the changing needs of the crew. When a voyage becomes active, it becomes its own project within the Asana structure. The navigator plays a critical role in ensuring the voyage backlog's smooth operation and the contributions of all crew members. This responsibility includes organizing weekly meetings to discuss voyage proposals, priorities, marketing strategies, and other related topics. Furthermore, each crew member, regardless of their role, is encouraged to contribute at least six voyage ideas to the backlog.
# Tidied Transcript
The Voyage backlog is a project within Asana. Specifically, it's a column in the Asana project called "Asal Voyages," where a prioritized list of all suggested voyages is kept. This list is compiled from suggestions made by crew members and external parties. The navigator is responsible for collecting these voyage suggestions from the team and soliciting them from external sources. When we start marketing voyages, they will be added to the backlog and prioritized. We hope to have more demand for voyages than we can deliver, so this backlog will be used to determine which voyages to pursue. Since we anticipate having to actively market voyages, we will prioritize the ones we believe are most beneficial to pursue and then seek customers for them. The process of managing this involves several steps. Firstly, we aim to have six voyages detailed on our website by Earth Day, and ideally by the London March event. This would involve creating a detailed webpage for each voyage, complete with images, text, contact information for the responsible team member, and other necessary content. A corresponding task in the backlog should be created for each voyage. This task should include a summary of the voyage and a link to the relevant Obsidian wiki page. These tasks can then be moved up or down in the backlog based on priority. At meetings, we will discuss the voyages we're piloting and adjust their priorities as needed. We can also create subtasks for each voyage. If a voyage becomes an active project we're working on, it will need to be a separate project within Asana, such as "The Governance Voyage." This project will exist within the Astral Voyages backlog project but will also have its own space for expansion. Typically, there is a mapping between a project and a website. For example, if we had a project in Asana called "Governance Voyage," there should be a corresponding website with a URL like governance.voyage.astralship.wiki. Next, it's important to note the role of crew members and the navigator in managing this task. Each crew member, whether they're the cook, engineer, navigator, captain, or magician, is responsible for their area of the project. They are required to provide input from their perspective on which voyages we should pursue. This means that they are obligated to suggest voyages they believe the project should undertake. Some crew members may be naturally inclined to suggest ideas, while others may hold back out of uncertainty or self-doubt. However, for the sake of collective intelligence, diversity, and good decision-making, we need input from all perspectives. This is not just the responsibility of the navigator or captain, but of every team member. The goal is for every department to contribute six voyage suggestions to the backlog. If there are five departments, this would amount to 30 voyages on the backlog at any given time. If you're not someone who enjoys suggesting voyages, you can recruit a team member to help you, or ask for assistance from another team member. The important thing is that you fulfill your responsibility of coming up with six voyages, either by yourself or with help. Lastly, the navigator is responsible for getting the Voyage backlog project working. They can start by researching existing material around voyages and creating tasks for them. The navigator should then inform people of their responsibilities by assigning names to the tasks. It would be beneficial if the navigator could organize a weekly meeting to discuss the voyages, their web pages, marketing strategies, priorities, new ideas, and other related topics.
# Keywords Voyage backlog, Asana project, Navigator, Obsidian, Crew members, External parties, Prioritization, Voyage ideas, Active voyages, Weekly meetings, Webpage, Marketing strategies
# Graph
digraph { layout=fdp; "Voyage backlog" -> "Asana project"; "Voyage backlog" -> "Navigator"; "Asana project" -> "Active voyages"; "Navigator" -> "Crew members"; "Navigator" -> "External parties"; "Crew members" -> "Voyage ideas"; "External parties" -> "Voyage ideas"; "Voyage ideas" -> "Prioritization"; "Prioritization" -> "Active voyages"; "Active voyages" -> "Webpage"; "Webpage" -> "Marketing strategies"; "Marketing strategies" -> "Weekly meetings"; "Weekly meetings" -> "Navigator"; }
# Assets
voyage-backlog
# See also - Voice Notes
# Tools
The tools below will use generative AI to edit the contents of the page displayed above.
Tidy the raw transcript with generative AI: