WorkFlow
Bea adds Opportunities to the list.
A developer creates a Projects, and we maintain a proper argumentation process. Projects include small enhancements.
We greenlight projects at Hypertuesdays.
We execute the project, and Bea reviews the implementation, giving feedback to the project before completing the project.
If there is new feedback to a completed project, it is required to start the process again.
Old
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.