Any views expressed within media held on this service are those of the contributors, should not be taken as approved or endorsed by the University, and do not necessarily reflect the views of the University in respect of any particular issue.

Preparing for My Supervisor Meeting

Before my first supervisor meeting, I felt a little anxious—not because I didn’t have ideas, but because I had too many. I wrote up a one-page summary of my potential research topic and included three possible versions: one that involved interviews, one that used only literature, and one that was somewhere in between.

I also made a list of key questions: Is a literature-based project sufficient in scope? Should I focus on just one flower type, or compare a few? How can I ensure that my review speaks to real-world issues and not just stay theoretical? What form should the final output take—a formal academic paper or something more industry-oriented?

Preparing like this helped me clarify my thinking and feel more confident going in. I also reviewed the KIPP project plan structure and matched it to my draft ideas, so I could show my supervisor how I might map each section of the proposal.

During the meeting, I explained why I had concerns about feasibility if I pursued primary research. I mentioned the limitations of getting access to florists or small growers, and how a literature-based approach might still allow me to explore lifecycle comparisons and sustainability frameworks. My supervisor agreed and pointed out that a desk-based review could be very strong, especially if I focused on the logic and synthesis of what’s already been published.

In the end, the preparation paid off: I was able to present my project clearly, get useful feedback, and leave the meeting with a real sense of direction. It also helped me see the meeting not just as a check-in, but as a collaborative space where my uncertainty was welcomed, and my ideas could evolve.

 

Leave a reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

css.php

Report this page

To report inappropriate content on this page, please use the form below. Upon receiving your report, we will be in touch as per the Take Down Policy of the service.

Please note that personal data collected through this form is used and stored for the purposes of processing this report and communication with you.

If you are unable to report a concern about content via this form please contact the Service Owner.

Please enter an email address you wish to be contacted on. Please describe the unacceptable content in sufficient detail to allow us to locate it, and why you consider it to be unacceptable.
By submitting this report, you accept that it is accurate and that fraudulent or nuisance complaints may result in action by the University.

  Cancel