Skip to content

Posts from the ‘Uncategorized’ Category

Really good parallels: “The most contentious point between software engineering culture and visual design culture is the question of whether important things can be always seen in absolutes. The engineering approach values measurable, reproducible results which can be represented in a graph or a checklist. Unit tests and benchmarks illustrate progress.”^^^ yup, sounds like the DQI to me. “Visual design is often the polar opposite of engineering: trading hard edges for subjective decisions based on gut feelings and personal experiences. It’s messy, unpredictable, and notoriously hard to measure. The apparently erratic behavior of artists drives engineers bananas. Their decisions seem arbitrary and risk everything with no guaranteed benefit.” ^^^ if we see designers (Architects only?) as “artists” – in the sense that they are creating an artefact – then this also works. “Designers, though, are just as frustrated by the apparent blind allegiance to data at the cost of human experiences. They often feel as if engineers lose sight of the actual goal. Artists see data as a tool only, not a purpose onto itself. The reason for this is simple: data in isolation makes no guarantees about whether the correct thing is being measured, or whether the measuring itself is skewing the results.” ^^^ aka “designing by numbers” We need to consider the consequences of our measurements. A BQM alone won’t be enough. We also need to see numbers are guides rather an absolutes – although how will this sit in a positivist culture?

23 March 2009

Derek Thomson

Measuring the Design Process

Derek Thomson

American economist Richard Thaler, who discusses his book Nudge.

BBC Radio 4 – Start the Week – Mon, 23 Mar 2009 http://www.bbc.co.uk/iplayer/episode/b00j67mh/Start_the_Week_23_03_2009/ The principle could have relevance to design interpretation by stakeholders, but its’ premise is somewhat old-hat – e.g. the flies in the urinals in Schiphol airport. Actually, now that I’ve listened to it again – it’s not that relevant. A bit basic aside from the “nudge” buzzword. The concept of a snag or a bump in an economist’s model, or in a stakeholder’s perception / attention is interesting, however. They also talk about a “nudge” as if it’s a perversion of an intended behaviour pattern by users: maybe analogous to battles against architectures of control in building design and process design, perhaps???

Derek Thomson

Too late – off to bed – not like I’ve got hours and hours of teaching tomorrow, anyway. Hang on…

Derek Thomson

“Weak ties are not less valuable than strong ties, but more valuable: they need media through which they can develop”

^^^

CRITICAL – this would be the purpose of SNA use to stimuate innovation – to find the weak ties and provide them with resource.

Derek Thomson

My interpretation:

If your network contains people who are not in operaitonal proximity to you, they will not help you innovate.

Boundary objects

23 March 2009

Derek Thomson

Connected communities of practice become a collective – but temporary – “community of interest.”  These linked communities of practice will be in operational proximity of each other (with regard to the problem considered).

The “boundary object” is the problem.  It is the thing that connects the communities of practice because they each have a (different) interest in the object.

A boundary object could be machines, software, rules, procedures, etc. — anything imposed by the org’s technostructure.

“A boundary object has meaning within the conceptual knowledge systems of at least two communities of practice.”

INNOVATION and CREATIVITY result because the meaning (understanding) of the boundary object is NOT the same in the communities of practice – it is this difference in understanding that breeds innovation and creativity.

Operational proximity

23 March 2009

Derek Thomson

Can be physical proximity, but more importantly – cognitive / attitudinal proximity.

Operational proximity happens when

– people share the same physical space and

– share ownership of the same problem

you need both for operational proximity to occur.

Operational proximity introduces different points of view to a problem.  This “differentiation” happens easily in organisations because they form themselves into informal social groups (cliques??)

Differentiation happens when different groups have “Cognitive Separation” (Lorch) – i.e. a different point of view on the problem.

See Tagliaventi and Mattarelli (2006) – Human Relations J.

A barrier to operational proximity is “cognitive separation”

Technostructures

23 March 2009

Derek Thomson

“Technostructures” – e.g. Mintzberg – the work of the professional core is increasingly managed through application of a technostructure

– compare and contrast McDonalds with a University. — suggests “technostructures are getting stronger in Universities” – increasing dogma with increasing throughput.

Communities of practice

23 March 2009

Derek Thomson

A “community of practice” has a shared social process.  The identity of the community is built around what is shared – a conception, an informal process, etc.

Source ??? of “communities of practice” = Etienne Wenger 1998

Weak ties

23 March 2009

Derek Thomson

Innovations are stimulated / useful / likely ??? when they spread between communities of practice.

Without weak ties, there is no real diffusion of innovation – formal processes/structures arent relevant.

A community of practice may stagnate “turning core competencies into core rigidities” — phon: “selly-brown and doogan” – “innovation and use of VLEs”