Date/Timing: Still to be finally confirmed, but we’re shooting for August 11, 10am EST / 4pm CET (you can do the math for you timezone); we’re aiming at a 60 min window – still considering/debating if we should go for 90/120, but probably not this time.
Communication: Will remain on social media – main site for the time being is the one you’re reading right now; of course pending final result from the initial poll – but looks like majority votes for staying public with this (you know my vote – not being open here is really kind of contradictory to the idea)
Issue submission: As stated in yesterday’s post, we’ll also run through ad-hoc requests during the chat, but still will open for submission a few days before we run the event
Targets (I don’t want to be over-ambitious, but….):
1) Get it started
2) Get issues solved
3) Create open communities focussed on issues / ideas made available – where those communities might of course be of really short temporarily nature, i.e. until the issue is solved
4) Create a recurring event out of this – this of course will only happen if you get in and also motivate your friends / colleagues / customers / partners / suppliers / project members….)
5) With those targets we also move away from the “vote on idea” stuff – it’s all about getting stuff solved, not debate who’s got the “better” issue
Procedure: Those of you having participated in e.g. #CSCTechTalk on CrowdChat know how this runs – it’s an open discussion on the platform (final link will be published soon – probably https://www.crowdchat.net/SpeedIdeation) where all questions and answers are automatically posted on twitter. We’re looking into providing a follow-up platform for larger issues where teams will need to collaborate for an extended period of time. Other than in CSC’s standard TechTalks, there will be no Google hangout – we’ll focus on raising and solving issues, so educational part will not happen in this event.
Issue submission: Those of you who’d like to raise an issue before the event, please do comment on one of the posts, so we can approve – I don’t think we’ll have the bandwidth to do approvals 3 minutes before we start….so thanks for an early heads-up.
So, thanks again to everybody support this initiative – stay tuned, more updates soon
Luckily I had to drive for roughly 5 hours today and could do some brainstorming with Soren on the phone (short but significant) and myself (long with results to be reviewed by all of you)
Soren had a valid point when stating that long preparations are not really what we need in a #SpeedIdeation event, so let’s talk about the following:
a) We’ll reduce lead time to a minimum, i.e. participants can raise any issue also during the crowdchat – This would also cater for being able to raise current issues (development, business, anything you need to get done fast) – As this could lead to topics being raised where no experts present in the event, please make sure to activate everybody you know – the higher the participation, the better the results of course
b) We’ll still cater for early posting of stuff to be discussed – let’s say 1-3 days in advance – Keep in mind that a good description of what you want to get resolved helps to attract the right experts into the chat
c) Expected results – I would not expect we will be able to solve all issues raised within the event, so one outcome for a certain topic might be a group finding together committing to craft a solution (would hope this groups would then continue to report results via #SpeedIdeation and on this site
This initial poll (see polldaddy form below) just to find out where you’d like to share ideas that we’ll discuss and select in a later (soon) stage.
If you’d like to go open, please select “Public” – this would then probably be this or a similar site
If you’d like to initially present internally (please remember, the final discussion and voting / selection of winner will be in public anyway) please select “Internally” – this would then be within a company site also made available to other participants (like e.g. engage.csc.com) and restricted to registered users.
Let me know – and please share your vote using #SpeedIdeation tag
In yesterday’s CSC TechTalk Soundbites we’ve discussed setting up a speed ideation event. Here some initial thoughts on getting this started – please comment with your suggestions.
I still debate with myself (and probably have to take this also with colleagues and seniors) if the collection of issues & ideas to solve those should be done internally or publicly – at the moment I lean towards full external exposure, but this would require everybody to stick to a set of rules…let me have your thoughts on this.
b) Entering an idea
– Every idea should solve an issue – technical, business, social or whatever you deem appropriate – Issue and idea how to solve will be explained by person or group entering the idea – To be included in the documentation: — Negative impact of issues — Positive impact of suggested solution — Probability of suggested solution solving the issue — Efforts to shape, implement & manage solution
c) Timeline – all in one week
To keep this at the intended speed, there will be a window of 2 days to enter ideas (Monday & Tuesday), 2 days (Wednesday & Thursday) where all ideas are frozen but made available for public review, one or two hours on Friday where we will use #CrowdChat to defend and vote
d) What will happen afterwards?
This is the main topic we need to solve – although there’s already a great point in raising & justifying ideas, it would of course be way better if the chosen ones would be implemented; I’ll take this to the appropriate guys to check how we can inject into e.g. IRB or similar.
Again – please let me have your thoughts on this – and also (this is for @CSC colleagues) please let me know if you’d like to join in – there are quite a couple of tasks to be done to make this happen.
Update 2014-07-13: I activated portfolio on this site and created a new project. All future posts related to this project will be here (see also menu above)