On someone’s first day, I would focus on reducing uncertainty and helping them feel genuinely included. Before they arrive, I would make sure they have a clear schedule and understand what the day will look like. When they come in, I would personally greet them and introduce them to teammates with a bit of context about what each person works on. I would also help them get set up so they are not left figuring things out alone. Throughout the day, I would check in casually to see how they are feeling and whether they have questions. If possible, I would invite them to lunch or a coffee break to create space for relaxed conversation. Small gestures go a long way. When someone feels supported and comfortable asking questions, their confidence grows much faster and they can focus on doing their best work.

During a robotics team project, I noticed we kept running into integration issues — not because people lacked skill, but because communication between sub-teams wasn’t structured. Mechanical, electrical, and software were building in parallel without fully aligning on constraints. Instead of blaming anyone, I suggested creating a shared integration document outlining power requirements, connectors, and testing checkpoints. I also helped organize short weekly cross-team syncs to flag blockers early. As a result, we reduced last-minute debugging and improved overall team alignment. It taught me that many team problems are systems problems, and small structural fixes can make a big difference.

@irislifeonrecord, on IG