Exercise: Writing an Academic Article

Use technology to manage a bibliography, referencing and in-text citations.
This exercise introduces MS Word style sheets and References...

The following illustrative exercise uses the ECIS template on Google Drive (link).

1. Copy the template from the shared folder to your own computer.
2. Rename your file using the following pattern "Surname_MyResearchProject_YYYY.doc".
For example my own paper is going to be "HigginsEtAl_WorkingInVirtualLight_YYYY.doc". I have used the author convention "SurnameEtAl" as there are three or more authors.
3. From the MS Ribbon "Home" open the Styles Panel. The "Current style" field show the current text style wherever the cursor is in your Word file. Alternately navigate to top menu "Format>Style" for similar.

The current style at cursor location

4. Select section 1 "First level heading" and rename it "Introduction"

5. Paste and match formatting using following unformatted text as new paragraphs for section 1

Critical management studies appreciate that products and services, produced with technologies, by organisations, and the involvement of users, rely upon "actors having formal and symbolic resources for the exercise of... systematic forms of control over organisational participants, and indirectly over other groups and non-human objects"\citep{AlvDee2000aa}. The techniques and skill of management for producing digital goods and services (through software, hardware and systems) at its best aims to resolve this through the delicate, democratic balancing of power, control of resources, shaping of work culture, and leadership \citep{Kid1981aa}. The following brief introduction to the literature positions this study within the broad field of management information systems and seeks to inform further creative, design, and development initiatives.This study looks at...

6. Confirm that the paragraph current style is "Basic text"

7. Select the following text and change its style to "Subtle Emphasis". You many need to filter the style list selection at the bottom of the styles window.

“actors having formal and symbolic resources for the exercise of... systematic forms of control over organisational participants, and indirectly over other groups and non-human objects”

8. With the MS Ribbon "References" active...

Select the LaTeX citation command \citep{AlvDee2000aa} and replace it with the MS Word equivalent citation, i.e. from the References Ribbon select "Insert Citation". You may need to create a new entry in the Word file's Citations collection

Create a new citation source record

Enter a new source record as follows (n.b. add ", p. 7" to be thorough)

MS Word's new citation source editor

9. Similarly replace the LaTex/Bibtex command for Kidder "\citep{Kid1981aa}" with

Adding Tracy Kidder's Soul of a New Machine to the citation list in your MS Word document

10. Now regenerate the bibliography at the end of the draft paper by navigating to the "References" section, and selecting "Bibliography" to insert a new bibliography. You'll end up deleting the previous copy. You'll also need to reapply the style "Reference" to this text

n.b. the bibliography style-type (Harvard - Anglia) and the insert "Bibliography" command

For further background refer to the notes on the term paper at:
https://managingdesignanddevelopment.blogspot.com/2015/04/term-paper-and-presentation-guidelines.html

Writing styles: The term paper is written in an academic style, presenting your background reading, method, research, analysis, theorising and critiquing aspects, for example of the history, situation, processes etc of a particular sourcing context. Consider identifying an exemplary paper that you aspire to emulate or to compare your own paper with.

You must use the specified scientific conference template for the term-paper. Choose between either the LaTeX or Word template from the ECIS 2015 conference. Copies are available on (Google Drive link). By using and sticking with the ECIS template your paper will automatically conform with the scientific format guidelines for that conference.

Self-assessment for this exercise:

1. Did you upload the file (e.g. word file)?
2. Did you use the correct template?
3. Did you add a new source record into the document?
4. Did you insert a citation into the text of the document?
5. Did you regenerate the bibliography/references at the end of the document? 

Cultural probe method exercise

"Some complex design challenges involve people of different cultures, languages, and societies where traditional research approaches won't help us adequately emphathize with their experiences." (Battarbee et al., 2012: p. 7)

The cultural probe method encourages participants to make a visual journal and reflection of their encounter with a culture context/experience. Probes gathered and compared across many participants offer the possibility to provide both generalisable information and deep insights (potential for broad and/or deep learning).

The following exercise provides a 'flavour' of the method:

Suggested protocol to conduct a cultural probe as follows:

1. Take a trip to a local shop, market, or a specialist food store.
2. Purchase 1 inexpensive food item you never tried before (1x photo).
3. Research how to prepare it to eat or use it as an ingredient.
4. Follow the recipe to prepare the food and test it.
5. Write a paragraph-note summarising the exercise.
6. Findings: Captured in (at least) a 1+ photo and (at least) a 1+ paragraph-note.

Reflections from students:

"The homework’s cultural probe was an assignment that made me reflect on the concept of design empathy and the importance of investing yourself into new contexts and open your senses. The bad designs homework has for example made me look at the world in a different ways. I now notice things from a design perspective that I otherwise wouldn’t have noticed before."

"The cultural probe exercise was not a simple cooking exercise, for a first-time chef like me; it was an interest-oriented, research-based, process designed operation with excellent results."

Exercise: (b) Design a text-free search interface

Some hand-drawn ideas and doodles...

The goal of this exercise is to familiarise students with interface design approaches and tools. First by using pencil/pen and paper. Second by using the Balsamiq wire-frame tool to mock-up your design.

Objective
To practice creating design artifacts to display and test technology use/interaction ideas.

Material
A4 paper, pencil or pen.

Create an account on Balsamiq Cloud (no payment details are needed).

Log In to Balsamiq Cloud
https://balsamiq.cloud/#login

Instructions
1. Use paper/pencil sketch a mockup of a new kind of Internet ‘search page’ that doesn’t use text (at all)! (allocate 10")
2. Collect the sketches and display them to the class; allow the group to provide a brief commentary. (allocate 10" to display all mockups).
3. Next, use Balsamiq to create a digital version of the design. The new design may vary from the paper/pencil sketch. (allocate 15")
4. Discuss the following reflection points. (allocate 10")

Reflection
How did the quality and level of design discussion differ from the earlier exercise?
Comment on how you conceptualised or simulated the 'user' of your design.

References
Snyder, C. (2003) Paper Prototyping: The fast and easy way to design and refine user interfaces, San Francisco, CA, Morgan Kaufmann, Elsevier Science.

(other tools include: wireframe.cc, app.moqups.com, invisionapp.com, sketchapp.com, Axure, Justinmind, Marvelapp/POPapp and iRise)

---

Previous Student Examples

Dilyan's example: Fast booking mock up: Fast booking mock up

Whole class examples in collage:

Lean Software Development: An Agile Toolkit

Poppendieck & Poppendieck (2003) borrow the notion of 'lean' from Taiishi Ohno's Toyota Production System approach and adapt the system to software development. The guiding principle behind the idea of 'lean' software development is to eliminate waste in the form of inventory stock and piece work dwell times from any and every aspect of work possible. In borrowing lean principles and terminology, which were developed for physical goods manufacturing, how does 'lean' apply to software's 'perfect' manufacturing environment (perfection in this sense meaning to software's potential for its manufacture of exact copies of an original via digital copying)?

Waste is present in the guise of unnecessary formality and management overhead.

Extensive documentary efforts lead to waste, excessive communication (meetings) lead to waste, excessive processes, interruption, delays and defects all lead to waste in the software process.

Using the 'lean' model requires that we apply tests to work activities to establish their validity.
"A good test of the value of paperwork is to see if there is someone waiting for what is being produced." (Poppendieck & Poppendieck, 2003:5) They note that the most wasteful work around documentation efforts surrounds attempts to produce documents that "contain all of the information that the next person in line needs to know." (p7) Explicit documentation requires infeasible completeness; rely instead on tacit knowledge and direct communication between producer and receiver. The cases given in this book emphasise processes of communication, on incremental delivery, communication with customers, taking care to produce and give what is really needed, delivering simplest possible meaningful feature sets as quickly as possible.

All software is partially done, or rather is always potentially subject to change. Because software is amenable to change and its requirements are difficult to establish unambiguously software development processes are designed to reduce risk. Managing large software developments is an inherently risky process (Royce, 1970). In industry two polar extremes are taken by attempts to address risk: to establish perfect clarity prior to commencing the work, or to get feedback by producing something as early as possible (to give producer and customer a concrete artefact to explore, clarify, negotiate and make sense of. Lean takes the second position as its goal. P&P paraphrase Royce (1970) by stating that "every step in the waterfall process except analysis and coding is waste." (Poppendieck & Poppendieck, 2003:4). However Royce's own position was that "there are two essential steps common to all computer program developments, regardless of size or complexity. There is first an analysis step, followed second by a coding step... This sort of very simple implementation concept is in fact all that is required if the effort is sufficiently small and if the final product is to be operated by those who built it" (Royce, 1970: 328).

Value stream mapping is one way of describing the 'as-is' situation and preparing to change current processes and the balance of effort invested in development. Lean thinking applies the view that early feedback reduces waiting, the goal for which is to free the developer somewhat and the customer too, to give each the opportunity to clarify meaning and learn from each other what is desired, desirable, degrees of freedom and constraints. The implication of providing and giving early feedback is to recast the idea of who controls and manages development, instead control or management figure through involvement in production. Development may at this extreme be better understood as co-production. How then is this heightened communication between customer and developer attained?

References

• Poppendieck, M. & Poppendieck, T. (2003) Lean Software Development: An Agile Toolkit Upper Saddle River, NJ, USA, Addison Wesley.
• Royce, W. W. (1970) Managing Development of Large Scale Software Systems. IEEE WESCON. TRW. http://facweb.cs.depaul.edu/jhuang/is553/Royce.pdf

Notes:

SA 1: Is the use of a manufacturing metaphor in what is clearly a field of design and development work strictly applicable?

SA Note 1: The two fields of design and manufacturing are both conceptually and physically different. Certainly software duplication does not require the sorts of controls and efficiencies sought for in scaling production of physical goods manufacture. For digital media the finished product is absolutely the end of the story. More importantly, in the case of software a shift of focus from reproducing a digital good towards the work of designing the good is absolutely necessary. Software development's focus must be upon everything that precedes the production of the first copy of the end product. The manufacturing metaphor has limits when applied to software development however the principles of 'lean' are still relevant and applicable to software's activities: design, analysis, coding etc.

Good UI delivers visibility, feedback, control.

Golden Krishna's thoughts on 'NO UI' prompted a response by his colleague at Cooper Design, Stefan Klocek, who argued back that good UI can be, should be, is desirable. Design should not be about removing UI, but that good UI is instead about those three big things that Don Norman focuses on: visibility, feedback, control. Klocek's article is available from The Cooper Journal (link)

The best interface is no interface

Who doesn’t want Twitter inside the refrigerator? 

I'm sorry, Twitter in my refrigerator, why?

“Upgrade your life” with a better refrigerator door from Samsung and check Tweets when getting some water from the fridge?? 

 How do you make a better hotel lobby? Slap an interface in it. A giant touchscreen with news and weather is exactly what’s missing from my hotel stay?!?? Golden Krishna argues that our love for the digital interface has gotten out-of-control. With more than a touch of irony...

"Creative minds in technology should focus on solving problems. Not just make interfaces."

From The Cooper Journal (link)