Week 1–2: From Onboarding to My First Business Analysis Deliverables

Week 1–2: From Onboarding to My First Business Analysis Deliverables

Period: 2, 4–5, 8–12 June 2026

Starting my internship as a Business Analyst Intern has been an exciting journey filled with new experiences. From getting familiar with the organization and workplace tools to contributing to a real client project for the first time, these first two weeks have been both challenging and rewarding.

Week 1: Getting Started

2 June — Onboarding and Employment Contract

My first day focused on onboarding activities, where I was introduced to the organization, its working culture, and internal processes. I also completed the employment contract and other related administrative procedures.

This initial experience provided a solid understanding of the company’s environment.

4 June — Exploring Tools and Workflows

On this day, I familiarized myself with the systems and tools used within the organization, particularly Notion, which serves as a central platform for knowledge management, task tracking, and team collaboration.

Hands-on experience with the platform highlighted the importance of structured information management in supporting the work of a Business Analyst.

5 June — Revisiting Agile and Software Development

I spent time reviewing and deepening my understanding of Agile methodologies and software development processes. Although I had previously studied these concepts at university, exploring them in a real-world business context revealed new perspectives and practical insights.

What stood out the most was realizing that Agile is not merely a theoretical framework but an approach actively adopted by development teams to respond effectively to changing requirements and maintain flexibility throughout the project lifecycle.

Week 2: Entering My First Project

8 June — Project Onboarding

This marked my first day joining the Project. I attended an introduction session conducted by P’Tom, where the project objectives, workflows, and business requirements were explained.

Afterward, I was assigned my first task as a Business Analyst Intern: creating an As-is Journey Diagram using Draw.io to visualize the client’s current business processes. Throughout the process, P’Amp provided guidance and reviewed my work to ensure its accuracy.

For me, this was my first experience conducting process analysis based on a real client case.

9 June — Completing the As-is Journey Diagram

I continued working on the As-is Journey Diagram until it was completed. At the same time, I began studying Odoo, the ERP system that would play a significant role in the project.

Learning about Odoo helped me understand how business processes are closely connected with software systems that support organizational operations.

10 June — Designing the To-be Journey Diagram

Following a review session with P’Tom, I started designing the To-be Journey Diagram, which represents the future-state business process based on recommendations and improvement opportunities identified from the current workflow.

11 June — Finalizing To-be Journey and Creating EPICs

I completed the To-be Journey Diagram and began creating EPICs to organize requirements into high-level functional groups.

This activity provided valuable insight into one of the core responsibilities of a Business Analyst: translating business needs into actionable deliverables that development teams can implement.

12 June — Customer Review Session

I participated in an online meeting with the client to review the As-is Journey Diagram and validate whether it accurately reflected the client’s existing business processes and operational needs.

Following the meeting, I incorporated the feedback received to refine the diagram and improve its completeness and accuracy.

This experience reinforced the importance of stakeholder engagement, as discussions with actual users often reveal details and perspectives that may not be apparent during initial analysis.

Key Learnings

Throughout these first two weeks, I learned that the role of a Business Analyst extends far beyond documentation and requirement gathering. It involves understanding business contexts, communicating with stakeholders, analyzing processes, and transforming business needs into practical solutions that can be implemented effectively.

Moreover, working alongside experienced colleagues and receiving continuous guidance demonstrated how real-world experience complements academic knowledge. These early experiences have provided a strong foundation for my growth and development in the field of Business Analysis.