Not Signed-In
Which clippings match 'Problem Solving And Problem Finding' keyword pg.1 of 1
30 JULY 2012

Communicating and discovering insight through reflective journals

A reflective journal is both a communication tool and a design method for developing professional practice. Such journals allow designers to publish their projects as they progress and provide a platform for critically reflecting on creative works and the design process.

Reflective journals can be used to discover insight about how designers approach their creative problem–solving. This is commonly understood as a central requirement for designers to develop their professionalism and to become experts in the field. They do so through reflecting on their work – characterising common features and critically analysing successes and failures.

Reflective journals also help designers situate their work within the broader creative industries and contemporary visual culture context. Designers might use their journal to document developing trends and to collect examples of inspirational works. These collections might be made as part of the research phase of a given project or contribute to a more general understanding of a design field.

Such journals should take an appropriate form so that they communicate effectively and provide necessary insight. They might exist in a singular form e.g. a workbook, a weblog or they might exist as a collection e.g. as a workbook of sketches with notes/annotations and as a weblog/Tumblr of photographs/videos with associated critical reflections.

The following are examples of art and design reflective journals:



Simon Perkins
22 APRIL 2012

Cooperation and collaboration: problem solving and problem finding

"The economists Richard Lester and Michael Piore have studied the firms that sought to create the switching technology, finding that cooperation and collaboration within certain companies allowed them to make headway on the switching technology problem, whereas internal competition at other corporations diminished engineers' efforts to improve the quality of the switches. Motorola, a success story, developed what it called a 'technology shelf,' created by a small group of engineers, on which were placed possible technical solutions that other teams might use in the future; rather than trying to solve the problem outright, it developed tools whose immediate value was not clear. Nokia grappled with the problem in another collaborative way, creating an open–ended conversation among its engineers in which salespeople and designers were often included. The boundaries among business units in Nokia were deliberately ambiguous, because more than technical information was needed to get a feeling for the problem; lateral thinking was required. Lester and Piore describe the process of communication this entailed as 'fluid, context–dependent, undetermined.'[20]

By contrast, companies like Ericsson proceeded with more seeming clarity and discipline, dividing the problem into its parts. The birth of the new switch was intended to occur through 'the exchange of information' among offices 'rather than the cultivation of an interpretative community.'[21] Rigidly organized, Ericsson fell away. It did eventually solve the switching technology problem, but with greater difficulty; different offices protected their turf. In any organization, individuals or teams that compete and are rewarded for doing better than others will hoard information. In technology firms, hoarding information particularly disables good work.

The corporations that succeeded through cooperation shared with the Linux community that experimental mark of technological craftsmanship, the intimate, fluid join between problem solving and problem finding. Within the framework of competition, by contrast, clear standards of achievement and closure are needed to measure performance and to dole out rewards.

[20] Richard K. Lester and Michael J. Piore, Innovation, the Missing Dimension (Cambridge, Mass.: Harvard University Press, 2004), 98.

[21] Ibid., 104."

(Richard Sennett, 2008, pp.32–33)

1). Sennett, R. (2008). "The Craftsman". New Haven & London, Yale University Press.


2008boundaries • business units • clarity and discipline • closurecollaborationcommunicationcommunication processcompetitioncompetitive teams • context-dependent communication • cooperationcooperation and collaborationcorporationscraftsmanship • deliberately ambiguous • designers • dividing problems into parts • dole out rewards • engagementengineers • fluid communication • framework of competition • hoarding information • information exchangeinformation in context • internal competition • interpretative community • lateral thinkingLinux • Linux community • measure performance • Michael Piore • MotorolaNokia • open-ended conversation • participationperformanceperformativityproblem findingproblem solving and problem findingproblem-solvingreward • Richard Lester • Richard SennettsalespeopleshareSony Ericssonstandards of achievementsuccess • switching technology • technical information • technical solutions • technological craftsmanship • technology shelf • The Craftsman • undetermined communication • working methods


Simon Perkins

to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.