u/NoAppointment4009

Kurze Frage in die Runde: wie macht ihr aktuell eigentlich die Dokumentation eurer Pflanzenschutzmaßnahmen? Und wie viel Aufwand ist das für euch?

There's a gap between "being good at your job" and "being given a project to lead." Nobody prepares you for it. You go from executing tasks to managing expectations, budgets, and people who don't report to you.

I've talked to a lot of people in this position. The ones who struggle most aren't bad at their jobs. They just don't have the language for what's happening. They don't know what to call the problem, so they can't solve it.

Three things that made the biggest difference early on:

1. Understanding that "scope creep" isn't a failure of planning — it's a failure of stakeholder alignment before the project starts.
2. Learning that the kickoff meeting is already too late to align people. That work happens before it.
3. Knowing that the most useful skill in a project isn't planning — it's knowing which conversations to have with which person, and in what order.

None of this is in any onboarding program or PM course, at least not in those I have joined. Most of it you're supposed to figure out by watching senior people for years.

What do you wish someone had told you when you first got handed a project? I'm building something around this exact gap and would love to hear what the actual pain points are.