Skip to content

Advisory Report

In creative technology projects, writing an advisory report is about more than sharing your opinion. Your recommendations must be supported with facts, data, and insights from previous phases of the project. Instead of “I think this works,” you show why your advice makes sense by pointing to user tests, research data, best practices, or relevant theory.

Why is this relevant to you as a Creative Technologist? Because you will often advise clients, teachers, or your own project team on the best technological or design approach. A strong advisory report helps others understand not only what you recommend, but also why. For example, when recommending an interaction design for a museum installation, you might compare two sensor setups, present test results, and then argue for the option that best fits the visitor experience.

In addition to the content, how you present your advice matters. An advisory report should be clearly structured, concise, and adapted to your audience. This means building your advice logically (introduction with context, analysis results, comparison of options, recommendation, and conclusion) and avoiding jargon unless you explain it. Visual clarity is just as important: use headings, lists, and diagrams to help readers grasp the core quickly.

Starting Points

  • Explore general guidelines: Advice Report (taalwinkel)
  • Collect concrete evidence from your project: user test results, performance measurements, or prototypes.
    Example: “Prototype A detected 90% of color changes, while Prototype B only 60%.”
  • Identify your target audience: a client may prefer a high-level overview, while fellow technologists need more technical detail.

Key Points

  • Use a logical structure: start with context and problem statement, then present analysis and alternatives, and end with a clear recommendation.
  • Base your advice on concrete findings (figures, research, examples) and explicitly refer to them in your justification.
  • Show alternatives and explain pros and cons for each, so your recommendation is transparent.
  • Write clearly and concisely; avoid unnecessary jargon and long, vague sentences.
  • Adapt your document to your reader: stakeholders need clarity, technologists may need depth.
  • Ensure visual clarity: use headings, bullet points, and diagrams where helpful.