CAPTION TEXT

Abstract[edit | edit source]

Short abstract describing the project from background to conclusion. This should be about a paragraph long and cover the main topic of each of the sections from start to finish.

Background[edit | edit source]

Describe the background of the project. Make sure to cover who, what, why, when and where. This is not the problem statement. It is the background that readers should understand before the problem. Remember that the reader does not know anything about the project, except what you covered in the abstract above.

Empathy[edit | edit source]

Describe your various processes for collecting information. Summarize the results. Include some pictures. Include some specific demonstrative anecdotes.

Interviews[edit | edit source]

Summarize the various interviews and interview processes that you utilized.

Community meetings[edit | edit source]

Summarize the various community meetings and and meeting processes that you utilized.

Observations[edit | edit source]

Summarize the various observations and and observations processes that you utilized. Feel free to add or subtract subheadings under empathy as needed.

Literature Review[edit | edit source]

I think we might skip this just this time... feel free to wait until I arrive to complete the literature review subsection. Introduce the literature review briefly and then use heading and subheadings for topics. This should focus on information… NO PLAGIARISM! [1] Copy and paste from this Practivistas India/literature review template.

Definition[edit | edit source]

Problem statement[edit | edit source]

Start your project objective statement in the format, "The objective of this project is to..." Feel free to include specification and considerations here, or make subsections for them.

Criteria[edit | edit source]

Include a brief intro to the criteria and then include a table with constraints and weights (0-10 highest). Edit the code below to make your table.

Criteria Constraints Weight (0-10)
Criterion 1 The constraint specifically on criterion 1 The weight for the criterion
e.g. cost e.g. must cost less that $10 USD per year. e.g. 9
Criterion 3 The constraint specifically on criterion 3 The weight for the criterion
Criterion 4 The constraint specifically on criterion 4 The weight for the criterion
Criterion 5 The constraint specifically on criterion 5 The weight for the criterion

Ideation[edit | edit source]

Describe your ideation process. Include some images of your process, and include community ideation as well. You do not need photos of everything. Feel free to describe in words, and summarize/generalize repetitive processes.

Prototyping[edit | edit source]

Describe your various processes for prototyping for function and desire. You will need to make some executive decisions on what to include and what not to include. It is important that the major prototyping tracks are described, including the ones that ended in 'failure'.

Make subsections for each of the prototypes and give it a better subsection title than this[edit | edit source]

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Make subsections for each of the prototypes and give it a better subsection title than this[edit | edit source]

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Make subsections for each of the prototypes and give it a better subsection title than this[edit | edit source]

Describe what you were trying to prototype, what questions you were hoping to answer, include photos in a gallery as shown below. Also, do not forget that all photos should have a very unique name, e.g. Communityname_Prototypename_1.jpg.

Describe the results of each of the prototypes.

Tests[edit | edit source]

Describe testing results or culminations events such as a fair. You may need to make multiple subsections here using the three equal signs on either side of the subsection name. This will include lots of photos, which may be in gallery format or using the image code and switching between left and right orientations.

Timeline[edit | edit source]

Introduce the timeline and include a table of the timeline. Briefly describe what you did each day. Alternatively, this could be a link to a google spreadsheet as long as it is one that will not go away (i.e. it should probably be shared via Meenal or Lonny.

Conclusion[edit | edit source]

Describe your tangible findings.

Instructions[edit | edit source]

This is how to make, use and/or maintain it. The step by step how to template {{How to}} is most likely best for this part as shown below:

How to Do Something:

1
Write some hover text, which can be the same as the description.
Write a caption that fully describes this step.
2
Write some hover text, which can be the same as the description.
Write a caption that fully describes this step.
3
Write some hover text, which can be the same as the description.
Write a caption that fully describes this step.
4
Write some hover text, which can be the same as the description.
Write a caption that fully describes this step.

Troubleshooting[edit | edit source]

This is only how to troubleshoot basic operation. For complex issues, the solution might just say contact ________. In addition, this might not be relevant to your project... if that is the case, just delete this section. It should be a table in this format:

Problem Suggestion
Example issue Example solution or suggestion
Does not turn on Make sure it is plugged in
Another issue Et cetera

Discussion[edit | edit source]

Discuss your findings through your own lenses. Summarize and editorialize. These can be more subjective, just make that clear.

Lessons learned[edit | edit source]

Describe your collective lessons learned in the project.... most likely in a numbered bullet format as shown below:

  1. Check in with your team daily
  2. Address communications issues early
  3. When inventing a widget, make sure that widget doesn't already exist in the local store
  4. Etc.

Next steps[edit | edit source]

Discuss any next steps for the project as it goes on into the future.

Team[edit | edit source]

Introduce team member name in the following format:

References[edit | edit source]

Make sure to include other relevant categories at the bottom, e.g. [[Category:Rainater]], [[Category:Upcycling]], etc.