But is it your job to know how it works? If the answer is no, then why are people asking you how it works? If the answer is yes, and you are responsible for it than how does this problem get resolved? You can’t hide in a sea of unknowns if you are supposed to know how it works – no amount of diagrams or technical jargon will keep the problem hidden.
Big deadlines, and big deliveries, no matter the level of planning you do, will always require some extra effort. There is no way around it, irrespective of the field you are in, that extra push always needs to happen. You hope for it to be a week, but then a week turns to 2 and then into a month. This is where your team needs your leadership, your guidance, and your experience to know when…
If it’s not organized, organize it. If the current code doesn’t work, fix it. If the words don’t fit, rewrite them. If the team is suffering, get them together, and figure it out. If you see the problem, jump in. You don’t have to have all the answers or the final solution. You do have to be willing to take that first leap to make the change happen. Otherwise, sit, complain, stew, grumble, sulk -…
You don’t just start trusting each other. It’s not something that happens on the first, second, thirtieth, or seven thousandth day. It just happens. It happens when the team has put in the daily bits to make it happen. It happens when the team has put in the effort to get there. It happens when the team has committed to the result, irrespective of the costs. Don’t force it, guide it, support it, then it…
Tools are great for making tasks you know and understand go faster. I.e., I know how to use a screwdriver, a drill is much faster, and the purpose of the drill is to make holes and screw in screws faster. I know the problem, I have the solution. However, if you are buying a tool that you “think” will solve a problem, but doesn’t really and adds a lot of overhead to what you are…