infoarch

Working together is great - most of the time. I really enjoy working with other people on tasks, instead of alone. Usually it's more fun, we get to results faster, the results are better, etc. But how often do we give 'working together' some thought? What I see is lots of time is spent on who should we work with and for ("who are our stakeholders?"), when the work should be done and what the objective of the tasks is. But how often do we think about the 'how' of working and what this means for the 'what' and 'when'? Deliberately thinking about how we are working to get better results. I think we should do this more and recently a great report was published to help us all do this more. Martin White recently wrote an interesting research paper about 'working together' . First I thought it was 'only' about meetings, live and virtual. And if the report was just about meetings, it would have been valuable enough. My expe...

Oof, really have to get back to blogging... I've been very busy with a product creation process re-engineering project. In general terms it's business process re-engineering. Recently the business team release their process descriptions, way of working descriptions and requirements to manage the processes. I'm in the Architecture Team, but also one of the Functional Team members. So now it was our turn to take the requirements and flip them into a functional specification. Interesting but cumbersome work... As I tweeted I'm also reading Chris Anderson's book 'Free'. And I'm really enjoying it! One of the interesting remarks he makes is: every that goes from atoms to bit will be 'free'. But Chris Anderson doesn't stop thinking. In the last Wired issues he says the following. Very interesting stuff! "Peer production, open source, crowdsourcing, user-generated content — all these digital trends have begun to play out in the world of atoms,...