SUW- SKO reflection week 5

Please look at the following reference on reflection and use it to inform your week 5 SUW writing that needs to be completed in your SKO diary in your personal assessment folder.

(Aim for 10-20 mins uninterrupted writing – remember this forms part of your SKO assessment and we will be catching up on these next week in the studio)

Ryan, Mary, and Michael Ryan. “Teaching and Assessing Reflection in Higher Education.” Queensland University of Technology, Brisbane. 2012. Seminar, Centre for Recording Achievement, QUT Draw Project. – Reflection slide from the presentation – The 4 Rs for Reflective Thinking

Try writing a reflection that works from the 4 headings Reporting, Relating, Reasoning, Reconstructing.

Concepts research stage (methods)

If your group is floundering on what move to make next with the concepts research. The IDEO HCD handbook has a variation of methods that you could utilise to start co-designing with your stakeholders.

Check the ‘Methods’ section p.26-60. – see how many of these activities you may be able to use to research over the next 3 weeks – split your group up to work on varying methods to engage with your stakeholders.

Week 5A studio preparation tasks.

It would be great for groups to respond to the following activities before the first week 5 studio on Wednesday.

1. Presentation debrief – Please add in your comments to this google-doc to get this conversation happening in the studio in advance.

2. Problem statements – Thanks for getting in your return briefs yesterday. We will check the submission of these in the studio on Wednesday. Following up on the clients’ feedback on Friday before we move to starting ‘Brief 3: Concepts’ we need to write up revised problem statements for each of the projects and get these to Lentara for feedback and final clarification. Based on the feedback you got last Friday could each group add their revised problem statement to this shared g-doc under your group no.

3. Collaboration contracts – The other thing we need to establish as we move into the heavy lifting part of the studio (producing concepts and prototypes) is some agreed ways that you as a group will work on projects – the governance of your project team. The governance you put in place will affect the assessment of your group projects. Please refer to the Collaborative contract pro-forma document before the studio and begin planning how you will document meetings and the activities of each group member for potentially reporting issues back to the studio leads.

SKO reflection – week 4

For you weekly SUW (shut-up-and-write) reflection this week take just (10 minutes) out to SUW and write a week 4 reflection in your Brief 1/SKO diaries in your personal assessment folders that were shared to you.

Please make sure you complete these reflections each week in the same google-doc as this forms part of your assessment.

For this week it would be great if everybody could write about the experience of the Transition Design workshop “futuring exercise” – casting your problem out 10 years from now to see what the issues you are exploring might look like.

I certainly found this a challenging but beneficial thing to do in regards to seeing beyond the immediate need to find a solutions or ways to improve the issues at hand.

Brief 2 – Presentation tips

Some guidance for the presentations on Friday.

Firstly, we have packed a lot into this messy co-design “design criteria and ideas” phase that is Brief 2. In regards to time things are beginning to move pretty quickly so it is important for project groups to use their time wisely.

Working from the TD workshop today this is my advice in regards to bringing your presentations together:

1. Slow the process down a bit and think through the key objectives of Brief 2, which is mainly to clarify what you think the Lentara wants you to do – what they need help with…

2. Presentation duration – aim for around 10 minutes maximum (ignore my 15 mins in Brief 2) so we can use time for discussion with the client – as the main aim of Friday is to utilise the client interaction to improve your submission for the Sunday night deadline.

3. My advice for the presentation structure.

a. Start with context – remind us of what your project is…what you think the key problem is that you are being asked to address by Lentara. Prepare this by returning to the original project summaries (written by Gemma) in the project group selections document…Then look at the group (1 sentence) statement you wrote prior to the TD workshop. Finally, evaluate what the TD workshop produced for you in regards to clarifying or shifting that problem statement. Once you have the revised statement write it up and open your presentation with it. Be prepared to explain how projecting your problem into the future and then backcasting to now altered and clarified what you think the problem is…In here you may wish to show to the audience the iterative development of your problem statement from Gemma’s summary to what you have now…

b. Once you have the context sorted – then think about using your return brief to guide the rest of the presentation (as part of double-dipping your efforts). Background – presenting in summary your understanding of how your project fits within Lentara. From here move to Objectives, Target Audience, Message, Tone and Competition – if time allows touch on scheduling and budget. Some of these parts may be hard to flesh out so put your energy into the problem, objectives and message.

c. Major tip – we are not looking for creative ideas, solutions here – the focus of the return brief, the assessment, the interaction with the client is on working out what the problem is… what the project is…what the client expectations are…

d. Bring your global mood board research into this presentation where you think it fits (objectives, message…competition…) – but again use it as a secondary aspect to determine with the client the key objectives of your project. For example, case studies of similar projects may be used to argue what you think your project (problem) is…

e. Visual presentation tips – no bullet points (Boring!!) use text sparingly like a few words on one slide to get a point across – speak to that text and elaborate verbally rather than with bullet points; use lots of images (pictures tell a 1000 words as the saying goes..) – research online good presentation techniques – we are going to being presenting a lot in this studio so now is the time to develop that skill – you can see already how important it is to be able to communicate the complexities of what we are working on to others in the studio and beyond… to the client…and then later the people you work with at Lentara…and then beyond Lentara publicaly within the university and potentially to local and global audiences

Group problems for TD Workshop

Here (below) is the space for the Wednesday Transition Design workshop with SIX interactive canvas screens to put your group problems up on. Please can you get your groups to complete a group problem (ONE sentence statement) in the studio Google Community under your group category before Wednesday morning.

Previous ‘problem space’ post on this studio task.

Week 3 – Transition Design Workshop preparation

On Wednesday 22 March we will run the studio in the new RMIT Experience Design Centre.

Please meet in our normal room (9.3.6) at 9:30am sharp then we will walk together to the EDC. The EDC is a new augmented space designed explicitly to help co-design around ‘wicked problems’ of the type you are all confronted with now.

Together we will workshop each group’s ‘problem space’, using Transition Design methods.

Here’s 4 pages from the primer on Transition Design: Transition_Design_Monograph_edited_v2-1ehzhl9 (and here’s a link to the full document with extensive references).

Here’s Herbst Rittel’s original ‘wicked problem’ paper: 081012_Rittel_Wicked_Problems_Papers_Ken-1p6di1d *

Here’s design council UK’s articulation of the ‘double diamond’ design process: http://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond

thanks

Neal