Leadership Learning (The real problem was not technical)
This was the biggest realization:
---- Projects don’t fail because of bad electronics or code.
---- They fail because of bad coordination.
During Teknofest, I saw this happen firsthand:
- Work piled up on just 1-2 people
- Others wanted to contribute, but were not given ownership
- Internal conflict → blame game → slow progress
- Result → work got completed after submission deadline
At that time, I wasn't in any lead role.
I was just a team member watching things collapse silently.
But that failure taught me something priceless:
---- Leadership = distributing work, not controlling work.
What Changed Next (InSpace / ISRO Competition)
In the next competition (ISRO-InSpace):
- I started taking responsibility
- Clearly assigned ownership to every member
- Ensured accountability + regular updates
- No ego, no “I did everything”, only team-first mindset
Outcome → We won 🥈 2nd Prize (National)
Link
That win didn't happen because of better circuits.
It happened because of better teamwork.
Key Lessons Learned
| Lesson Learned | Short Explanation |
|---|---|
| Coordination > Individual brilliance | Even the smartest person cannot replace a coordinated team. |
| Ownership must be distributed | Everyone should own a meaningful deliverable, not just tasks. |
| Leadership is a responsibility, not control | A leader creates space for others to contribute, not dominate. |
| Credit-sharing avoids ego clashes | “We built it” works. “I built it” breaks teams. |
| Time management decides qualification | Work completed late is counted as work not done. |
One Line Summary
Teknofest taught me that technical skills make projects.
Leadership makes them succeed.
