Use case development – Proposed work threads

Noise management – as the network grows – more of a chance for noise – more likely to fragment and disintegrate based on that noise

  • approaches -  hidden follow button – practical 100-150 person limit
  • provide segregation – groups/communities/ – re-silo’d  – dilutes the social mechanism
  • use cases to articulate the problem, how to solve, see if we can learn from this

examples: – mixing a variety of information sources – what is the right method to change from noise to value – a user mechanism (custom views/aggregation – third party aggregation)  bringing things together replacing the follow model – segregation) – context aware approaches, introduce high energy content/hot topics, we know that things are silo’d – bring additional information (e.g. role relevant)

  • - letting the user manage the content without degenerating to self-siloing
  • - better tools to tune/re-tune the view
  • - counter self-selection and silos by introducing additional content back

- Implications of engaging with new people, how much to disclose, how to introduce additional participants (based as context and security without over disclosing)

Proposed out come: how do we stitch together an example and then create a POV on addressing – generalized use case (explain problem/define requirements for a proof of concept)

  • find a way to keep connecting people and information – preserving and extending the value of social
  • avoid having a new skin over an old problem

Questions:

  1. how do we bring background / corroborating information
  2. how to build a straw-man that resonates with the community, and can be iterated
  3. how do we make this actionable – what’s the engage model that creates value(usable information (maturity)) and draw into engaging – create an event

Comments are closed.