Communication
Every message that requires the team to think goes in Seed.
Casual conversations happen on Discord.
If you need someone to take action, use Discord.
For bug or issue context, use Linear.
Feedback Loop Process
Inspired by Design Process and User Story Mapping:
Identify and define the pain or problem as precisely as possible.
Design the Solution
Collective Effort:
State a clear Outcome.
Short descriptions of the User Stories that each of us have in mind.
Inspirations from other apps that each of us have in mind.
Sketches with idea that each of us have in mind.
Both Ux and Technical Pros and Cons from everybody on the team.
Voting the Best Solution.
Hopefully there is consensus on the team. If not Gabo is the decision maker of last resource.
Designer Effort:
State Clear User Goals through the User Stories.
What information must the user learn to accomplish the goal.
What are the User Steps.
Final Pixel Perfect Designs.
Implement a Feature on Project with the User Outcome in mind.
When there are changes to the Design, please ask Isabella Velez with cc Gabo H Beaumont.
Isabella Velez and Gabo H Beaumont Review the New Feature on a Monday Design Meeting, taking Notes.
User Tasks and User Stories.
Review Outcome.
Create Linear Tasks to Dev Team.
Talk to users and check the Outcome contrasting the User Task and the Solution.
Keep iterating the solution.
Move on to a more valuable opportunity to improve Outcomes.
Create concrete Tasks in Linear. Linear is used only to track the Tasks and not to do the Thinking.
Create bidirectional links between Linear and Seed Hypermedia.
Project Process
Our work is organized into projects that move through the following funnel:
Spontaneous Ideas: Everyone on the team is expected to contribute ideas for improving the product, in the form of Notes or unstructured Comments. Link your ideas to relevant Roadmap items, Story Map, the Human Interface Library, and Definitions so they can be easily discovered in the future.
Write Pitches: When an idea becomes essential, its owner should develop it into a well-defined project proposal. Involve developer, and Isabella Velez
Approve Projects: Projects are approved during Hypertuesdays. Each project should be scoped to last one, two, or at most three weeks.
Deliver Projects: Working software must be demoed on Tuesdays. The expectation is a high-quality, fully functional product. Define scoped projects to build them on time.
Project Document Structure
A project should originate from users’ conversations and needs. It’s unlikely that a Pitch will be approved if no users have expressed interest or requested it.
Problem.
Location on the Product Map: Clearly define where the project fits in the Product Map by mapping it to activities, user tasks, and user stories.
Solution.
Human Interface Library (HIL): Any related designs must be complete and published in the HIG section.
New Definitions: If the project introduces new concepts or terminology, these must be documented in the Definitions section.
Protocol Changes: If the project affects the Hypermedia Protocol, it must be accompanied by a dedicated document detailing the changes.
Rabbit Holes.
No Goes.
Due Date
Protocol Changes
Protocol changes that impact the permanent data. The process is long, if you need to deliver a new feature try building the logic at app layer without affecting the permanent data.
Note with a Request for Comments.
Argumentation mapping.
Decision not by consensus but by technical issues extenuation.
Change to the documentation on hyper.media.
Glossary
UX Pain
The feature doesn't provide the expected outcome or we need to create a new feature.
Bug
A Code problem.
Blocker
A user can't use the app.