Design: Reverse Engineering

Greetings

Reverse engineering is the process of systematically analysing an object (activity/concept/design/element/function/idea/problem/process/procedure/routine/structure/system...) specifically to ascertain the external (black box) structure/processes/inputs/outputs.. and/or internal (white box) structure/processes/funtions.. that contribute to its function and form

• The technique is used to breakdown an object/system (physical/actual or hypothetical/proposed) to facilitate our understanding and learning of that object/system

• For a hypothetical/proposed design/system the analysis can facilitate understanding of the energy/materials/... required to implement/manage the design/system

• The 5 Whys strategy of questioning is a type of reverse engineering used in Root Cause Analysis problem solving

Chew 

Mnemonic: SING - How to remember what you read

Greetings

Remembering read information takes an effort, especially when reading information/data in text books that will probably only be read once

• Note taking (in any form) is a good way of recording the information for learning, but how do I remember both the background information and the data to make it useful information in the future
• I came across the mnemonic below on a Youtube clip How to remember what you read, which fits in with the way I remember what I read 

Stop - at end of text/passage for a second to focus on the read text

Identify - the main point/s of the text. Stories are hierarchical. Focus on retaining the points

Never - mind the details. Focus on the point/s

Gist; get the - of the story. Overall - all point/s together 

Other techniques I use to remember read information include: 

• Reading the contents pages of a book prior to reading the book, a primer to understanding the gist of a book (see I and G above)
• If I'm bored I will also skim the index pages in the same manner
• Reading the first few paragraphs/pages of a chapter and then skipping to the last paragraphs/page
• Text book chapters will begin with an introduction to the contents of the chapter (the first few paragraphs/pages) and end with a conclusion (the last few paragraphs/pages)
• The information in between/the bulk of the chapter is simply discussion and only of further interest if required to understand the conclusion (see N above)

Chew

Design Notes: Community gardens public work day site managment

Below are a few notes triggered by a working bee to stimulate some design thinking. The notes apply for general working bee/site/hui/project management/implementation tasks, not specifically to the working bee itself

• Delegate a site/bee/project manger/coordinator
• Front of house/greet/introduce
• Identifiable (safety vest)
• Link between groups/people on site (OST butterfly)
• Knows where people/facilities are: water/first aid kit/toilet/tools/membership forms etc... and what is going on during the bee
• Ensures everybody finishes on schedule and site is tidy for shared food/time
• Be aware of constraints time/hands/manpower etc...
• Send arrivals to site/bee manger/coordinator for briefing/direction/safety drill/muster point etc
• Visitors/contact record sheet
• Name badges      

• Prepare a noticeboard of tasks prior to people arriving
• Provides visibility of the big picture of the bee to both the workers and the manger
• Break large tasks down into small achievable tasks; Break large areas into small areas
• Allow people to chose what type of task they participate in on the basis of the task list (rather than seeking and being told)
• Get people to mark off their completed tasks, add the task to the board if it was not on the original list
• Facilitates/feeds back a visual sense of collective achievement
• Provides a record of the work
• Shows uncompleted tasks that form the basis for the next bee
• Helps show tasks that require further planning to fulfil
• Show start and end times for the bee. Allow people to schedule

• Ensure you can complete the task you are starting
• Work within the constraints time/hands/manpower etc...
• Assist someone to finish their task before requesting they stop and assist you
• Finish your current task before leaving to start another
• What is important is the number of tasks completed not how many are started

• Work to time
• Aim to have 3/4 of your task completed by half way through the period and completed well before the finish time
• lots of small completed tasks are preferable to large tasks which go over time
• Leave plenty of time for tidying up
• Have everything tidy and the site clean before serving food/beverage
• Everybody gets to celebrate the work done/completed together, cementing a sense of group/community achievement

• Designate a location for hand tools\site tools
• Borrow, use and return. Part of the task/job completion process

• Signs that answer common infrastructure questions: water/first aid kit/toilet etc...
• Site map indicating areas/sheds/names etc...

• Dont allow people to dump materials at the site
• The site should develop/evolve by design and strategy - Unless required as part of the design implementation or for repair, materials should not be accepted/stored
• Advertise what materials are required and which are not. Advise where alternative materials can be disposed of/donated

• An abundance of ad hoc materials leads to an abundance of equally ad hoc projects, with all the associated post project fallout and diversion of effort

• Devolop good housekeeping (5S) 
  

 Chew