This Topic covers the developments of a new piece of analysis and ideation for the Network functionality. It is based on the great work already done in the past, documented here.
Decks used for the team sessions (currently once every 3 weeks)
- Kickoff - includes agreements, team composition, plan
- Check in 1 - includes highlights from 1on1 chats, draft user stories
- Sketch shop - TBD
- Check in 2 (WIP) - Includes competitive landscape
The problem has been explored and explained as part of
Discovery Session: Networks (see pictures)
Global Gathering 2019 - Day 7 - Network (see pictures)
@Rachel Network MVP brief
Network 2.0 - Real Case Studies of the Problem (continuously updated, please add any relevant examples)
Beyond the operational day to day improvements of management of products and inventory for our users, there’s the underlying improvements in transparency.
Many ideas have been explored in the past, this initiative looks at assessing them, while also exploring new ones for the short and longer term. We will also prioritise those solutions, to potentially roll out small improvements early, and bigger redesigns later down the track once we have initial feedback and validation from users.
After the ideation sessions (planned for April), concepts will be presented and shared.
At a really high level
Team agreements definition
Shall not allow for scope to expand - Define a lean scope as a group and monitor it closely
Keep things moving - Even with a small subset of the team and try to facilitate sessions that simulate collaboration in the same room
Be transparent - Share decisions and rationale with instance managers so that the broader team can provide feedback
Plan validation with users in advance - It will be challenging to reach the diverse user base that will be impacted, so think about smart ways to test concepts
You can share your thoughts, ask questions and provide inputs in this Topic or join the conversation in the #network slack channel. We want to be as transparent as possible, as highlighted in one of the team agreements. We encourage everyone to be part of this, join the conversation if you want