Reflective Journal – Week 11

Description

In week 11, my team organised a key meeting. It aimed to implement the mentor’s feedback on the project and clarify the structure and logic of the report and presentation. In the meeting, we sorted out the business plan content by module. We focused on discussing financial forecasts and the prototype presentation. I mainly participated in confirming the presentation logic of financial data and assisted in optimising the interface design.

Feelings

At first, I was a little anxious and worried about time constraints and high communication costs. However, I was very pleased when team members showed their sense of responsibility and execution. This also made me more confident to advance to subsequent tasks. I also realised that my ability to integrate technical details and presentation logic has been exercised.

Evaluation

On the positive side, this meeting greatly improved the efficiency of team collaboration. This solved the problem of repeated report content and overlapping tasks. Everyone reached a consensus on role division and content sorting. The shortcomings are in the financial forecast part. Specifically, some members had inconsistent understandings of “cost classification” and “revenue structure”. This may lead to logical conflicts in the early version.

Analysis

This misunderstanding indicates that the team did not share enough information about the “business model” and “forecast assumptions” in the early stages. Evers et al. (2021) pointed out that entrepreneurial teams should make explainable predictions based on their understanding of the business model and growth path rather than precise estimates. This experience made me realise that financial forecasting is not just a mathematical calculation. It is also a deduction of business logic and emphasises consistency and rationality.

Conclusion

This meeting proved that timely proofreading and logical sorting can greatly reduce the cost of later integration. Moreover, I also realized that every member of the team needs to establish a common language in key modules, especially to maintain transparency at the financial and technical levels. This understanding of the logic of collaboration and role transparency will lay the foundation for me to coordinate projects in multi-functional teams or lead early-stage entrepreneurial projects in the future. In complex scenarios that require the integration of technology and finance, this “structured collaboration capability” will become a key competitive advantage (Meijer, 2013).

Action Plan

I will review the financial data and prototype presentation content. This can ensure that they match our customer positioning and value proposition. I will also participate in the final presentation rehearsal. This can help the team optimize the presentation rhythm and logical structure. This can further improve persuasiveness and time control (Barringer & Ireland, 2018).