Re:post
I just realised I posted my comment in the wrong thread:
"
I love the idea of EdgeRyders as ‘living tech’. So started working on a landing page and then stopped, I wanted to check-in and find out from everyone, what we think it should contain. I did however plugin an IRC channel, just because it’s super simple.
https://edgeryders.eu/page/connect
I think it should look friendly, with a logical information hierachy. What comes to mind (in order):
- Short summary of how EdgeRyders tend to communicate with each other.
- Wiki Banner/Button Link out
- Buttons: Community Call, Twitter Embed with mix of hashtags, Call a human
- ORG CHART?
- IRC Channel
- Top 5 popular threads on ER in that moment
Anything else?"
iamronen and K raise some important points about the platform and I really endorse the session that has been proposed.
I’d like though to add a few short thoughts; for me EdgeRyders is entirely contingent on face to face meetings, the notion of a landing strip which I proposed in the call the other day wasn’t intended to be seperate from such encounters - it was intended to be a place I could direct people towards after an initial encounter, so they can get a handle on how it actually works from a technical perspective.
This platform is massively messy, I’m okay with that, I think all emergent practice of this nature is symptomatic of such qualities - in fact I tend to seek out the messy spaces, it is for me a typical signifier for interesting projects and conversations. I find it difficult to trust anything that is too sure of itself and purpose. It also embodies the demand that’s put on the user: “if you do not build it, it will not get built”.
That said, there’s a lot of improvement that can be done and there is clearly a deficit of skillsets, for example EdgeRyders lacks video content that accurately describes its process and story for potential future EdgeRyders - to date what we have is a sort of quasi promotional content that is unsure of its audience. EdgeRyders as a whole has also always bias’d the highly digitally literate.
What I think we need at this point is (at least) user journeys - that take into account sense making and service design, that do not discount online and offline interaction but are equally accounted for. I’m not sure we should aspire to building the perfect platform with a seamless user interface (I just don’t think we’ll get there - because our needs are continuely evolving and our resource is low).
The original project within my understanding was grown with a snow ball effect in mind; peers were invited to join EdgeRyders based on individuals being able to communicate what they felt was valuable about EdgeRyders, if these new comers could identify similar value through their own experience, they would likely emulate their introduction to the platform by inviting their peers and thus the platform grew out with a mix of small clustered communities. This ensures EdgeRyders is able to continuely evolve and stimulate fresh ideas.
These are just a few thoughts, based on my own experience, I’d be happy at some point (when there is time) to begin to translate my approach to EdgeRyders into coherent user journeys as a way of identifying what might be improved.