Database Design Project: Reflective Piece
(Using Gibbs' Reflective Cycle)

Artefacts & Submissions Below

1. Description

This assignment involved designing and documenting a logical database as part of a team, acting as software consultants. The chosen project matched my current professional experience, so I naturally took the lead and carried out most of the technical work, including integrating systems like Retool and Power BI. My colleagues were happy to let me take charge and supported the project direction. Although I expected a high mark, the result was a 60%, which initially surprised me. Upon reviewing the feedback and watching the professor’s seminar, it became clear that I had misunderstood the core intent of the assignment.

2. Feelings

I felt confident going into the project because I had experience with similar database systems in my workplace. I believed that implementing what I already knew would naturally lead to a strong academic submission. While I was happy to take the lead and shoulder most of the work, I now realise I didn’t fully empower my teammates. The project felt like a one-person show. After receiving the feedback, my confidence dropped, but I couldn’t argue with what was said. I focused too much on documenting what I had already built at work and not enough on justifying the design choices academically, which was the true goal of the task.

3. Evaluation

Starting the project early gave me time to build the database model thoroughly and create visuals that I believed clearly represented the design. I maintained communication with my group and encouraged input where possible. I also created a team contract with roles and expectations, which gave us a basic structure and accountability.

However, there were several key issues. I felt a responsibility to “prove myself” to the team that invited me, which made me take on too much. Although well-intentioned, this approach underutilised the talents and perspectives of my peers. Our group discussions lacked real collaboration, with most ideas being my own. This also meant I didn’t practice how to lead effectively or delegate meaningfully. Most importantly, I misunderstood the assignment’s focus. Rather than exploring and justifying different database design options, I simply documented what I had already done before. This missed the point entirely.

4. Analysis

Reflecting on this experience, I’ve learned that being knowledgeable isn’t enough in an academic setting. I failed to engage in the level of critical thinking and justification required. I also missed the opportunity to facilitate genuine collaboration within the team. Leadership isn’t about doing everything myself, it’s about bringing out the strengths of others. Additionally, I realised the importance of aligning work closely with assignment expectations. Simply translating professional experience into academic output does not guarantee success.

5. Conclusion

In future group projects, I need to balance leadership with collaboration. I should listen more, delegate tasks properly, and focus on enabling contributions from others. I now understand the importance to read assignment briefs multiple times throughout an assinemnt to ensure the project aligns with the reqirements and doesn't stray from it as it progresses.

6. Action Plan

Next time, I’ll still start early and use a team contract, but I will provide everyone with clear objectives and space to contribute meaningfully. If I take on a leadership role, I’ll prioritise guidance over control. I’ll also make it a habit to revisit the assignment criteria at every major milestone, ensuring that my work remains focused on the academic goals. Most of all, I’ll remember that teamwork isn’t just about output, it’s about shared growth, responsibility, and reflection.

References

Project Artefacts

Below are the key artefacts from the group project. These files provide insight into our process, planning, and outcomes:

  • 📄 Final Project Submission

    The final report submitted for assessment, explaining our database design decisions and implementation.

  • 📊 Initial Proposal

    Our early-stage pitch outlining the scope and intended features of the database system.

  • 🤝 Group Contract

    An agreement between team members detailing roles, responsibilities, and expectations.

  • 📝 Meeting Minutes

    Documentation of key discussions, progress updates, and action points from team meetings.