Hello! It’s took a long time until i can get back to update this blog, hehe. Freelancing and doing regular hustle took more effort than i imagine before 😅.
But, anyway! In first quarter of the year i already got many projects from my company, one of them was creating new feature in other service which is i didn’t really involved in there. First of all, i felt clueless because i don’t want to be so reckless to take step in this project, moreover i didn’t really know the domain, which is make me more cautious to take an action (even though my company was okay about trial and error concept for each of project). So, how can i stay aligned with other team and my team? I will take a step back.
In these circumstances, where we usually didn’t really know what we should do, always align with the team or stakeholder first. Schedule a meeting with them early as you can, in this meeting you should ask to them:
Because you do alignment since from the beginning, it should avoid you from jump into conclusion disease, which is common for every project.
This disease was show symptoms that you already knew everything and you didn’t need to clarify with your team. It’s dangerous.
Because your conclusion maybe right, but it can be wrong too. So, with this alignment you take a step back and minimize your errors, with clarifying with your team and equate team perspective. From here you can make your to - do plan for this project.
You can define your plan with a step back action
During the project, before you execute your plan you must be have bunch of assumptions and questions. Don’t keep it to yourself! Share those to your team, perhaps they also have another assumptions too, and they want to prove those in this project.
You can make workshop together, define those with your team. List those assumptions and questions into your note, make it as a base or guidance for you during the project. With this activity, you also make a step back for doing something reckless. You equate your assumptions with team, if there is something wrong with your assumptions, team can correct or re-align it. Always define together with the team. This activity can be implemented in early phase (such as kick off meeting or alignment meeting)
When you already have solution and you will present it to your team, you think: wait.... is this best possible solution for this problem?
For avoiding your “jump into conclusion” disease, you can make a step back activity in this phase. Why we not creating solution together? With creating together you not only remove your jump into conclusion thing, but also you can gather feedback from your solution from your team. You also will get bunch of idea and can find best possible solution.