High-level vision, vision board and requirements - WIP
Timothy Broome
Posted on July 19, 2024
High Level Vision
As described in my intro-post; I want to create an app that allows me to log productive time and then allow the exploration of cross-sections of that data. Data should be visualised in a mixture of numerical totals as well as graphics to efficiently provide a range of perspectives in one view.
Important metrics are:
- productive time
- planning time
- tasks attempted (started)
- tasks completed
Useful additional context:
- Task size
- Task complexity
- Task readiness (can be executed)
To achieve this a level of task-management will be needed to log time against tasks. However the ui should me nimble and easy to navigate. I do not want to re-create Jira or monday.com. A task should be quick to add and have the minimal information. Additional resources should be provided through links; for example; a work Jira task, an image, a website etc.
Vision Board
When designing and to communicate a vision to others; I find it helpful to create a vision/mood-board of related UIs/apps/experiences etc. These can be labeled to add flavour
Enticing data visualisation views from Strava and Smashrun. This new app should attempt to re-create this experience but for productivity
Requirements
When embarking on a project it's important to formalise requirements at the start. There's often alot of excited discussion between stakeholders, designers, engineers. But its amazing how peoples minds-eyes can differ when it feels like there's a common understanding and consensus.
Even as a one-man project; once embarked on all the technical details needed to build a project; the context and relative importance of requirements can be lost. Requirements are the way-points/the map to guide engineers and stakeholders through a project, and ultimately provides the finish-line to aim for..
Posted on July 19, 2024
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.
Related
November 29, 2024