Mitch's dogfood feedback - how should we address some of the issues (particularly around header in the calendar)
David Allen follow-up
Alec sent an email about this - we have a plan for rolling the team into discussions re: dashboard and 0.7
Should we talk about this on Thursday when I present the stickie plan - I don't want the team to think we are leaving them behind in these activities
What are the next steps for dashboard design
Designer position update
Review of current projects and updates
Notes
Dogfood feedback
Most of Mitch's issues are addressed in bugs and items deferred to 0.7.
Mimi would like to do some collaborative brainstorming around the navigation/calendar header since we need to revisit this when we add the month view anyway.
Dashboard - David Allen Debrief
Overall, the day went well. Mimi's wishes she has started with more discussion of context and why we ended up with the design we did.
The afternoon session left some people a bit lost - we didn't get to the collaborative brainstorming.
2 areas to work on with devs
understand dashboard design for 0.7 +
understand gtd
Next steps for dashboard
Meet with Mitch - review design, get brain dump on ideas
Prepare presentation for larger group - how did we end up with gtd concepts, where the dashboard came from. Expose how we ended up making the decisions we did. Most of these decisions were made long ago.
Identify the weak points in current design, areas we want to revisit.
Schedule collaborative design sessions with the team to cover these areas.
Could start a spec for dashboard work part 1 - table bugs, work, widgets etc