https://tidyfirst.substack.com/p/complain-and-propose Software Design: Tidy First? SubscribeSign in Share this post # Software Design: Tidy First? Complain & Propose Copy link Facebook Email Notes More From the Archives Complain & Propose [https] Kent Beck Dec 27, 2024 50 Share this post # Software Design: Tidy First? Complain & Propose Copy link Facebook Email Notes More 5 6 Share Republished from July 2014. "Jean-Louis wants to see you in his office." My boss Eagle Burns' bald head disappeared from the door to my office. Something about his tone suggested that righteous indignation, which I had been nursing for several days, was not the right attitude to pack for my trip. I started getting scared. It was Apple 1988. Jean-Louis Gassee was head of engineering. He had a reputation as a fire-eater, someone who chewed fools up and spit them out. I had been foolish, it suddenly occurred to me. Do the math. I was a young, cocky engineer. I was sure I knew better than anyone what needed to be done. When a decision came down that I disagreed with, I shot off an email to JLG that made it clear just how stupid the decision was. A day later, I was summoned. JLG's office was on the same floor as mine, but I had never approached the sanctum. He was at least four levels up from me in hierarchy. Rumor had it that decorating his office had cost $100K, which was a fortune since everybody else was stuffed in cubes. When his admin passed me in, though, JLG was avuncular. "I read your message. I'd like you to think about it from my perspective for a moment. What am I going to do if I agree with you?" No idea. He must have been used to dumb silence. "I'm going to ask my report for a proposal. He's going to ask his report and so on [yes, completely male. Plus ca change...]. Eventually Eagle is going to ask you what to do. In all those layers, who knows what's going to happen to the question. "Here's what I want you to do. Rewrite your message and make a proposal for what we should do about it. That way you'll save us a week and you'll get to solve the problem you want to solve." I did. I don't remember what the issue was or what I wanted to happen or what actually happened. That was lesson number one--it's really not that big a deal, or at least hardly ever. always bundle a proposal with a complaint Lesson number two was to always bundle a proposal with a complaint. I've used that style daily in the intervening quarter century. If I need to vent or I need to think something through, I do it in private. If I'm going increase the scope of a communication, I always say what I would like to happen. Lesson three was the most important. Those words, "Think about it from my perspective," were a revelation. You mean you have a point of view and it's just as valid as mine and it might be different? I've spent that same quarter century trying to absorb and apply that lesson. Communicating begins by putting myself in the place of my reader, not demanding that they put themself in my place. Complain and propose. Bonus lesson for when I was the old guy: don't get caught up in young hotshots' emotions. Assume good intentions and lack of skills. Thanks, JLG. 50 Share this post # Software Design: Tidy First? Complain & Propose Copy link Facebook Email Notes More 5 6 Share Previous Discussion about this post Comments Restacks [htt] [ ] [ ] [ ] [ ] [htt] Vladimir Bychkovsky 7m Liked by Kent Beck I really like the constructive spirit of the "propose" step. If you have a proposal, it is a defiantly worth bringing it up. However, there is an anti-pattern in management that's says "don't bring me problems(=complaints), bring me solutions(=proposals)". Why is that an anti-pattern? It is because of the position in the hierarchy people may experience the effects of the problem, but the solution may need to be way broader/systematic. Their proposals will most likely make little sense because they see any part of the picture and they would not want to bring them, so the problem will remain unseen and unresolved. What to do instead? Invite people to share problems, even if they don't have good solutions. And look for a systemic root cause for a lot of problems at once. Expand full comment Reply Share [htt] Ben Kellie 2h Liked by Kent Beck Love this. In my past career as IC, then manager, then founder of my own company my rule was, "bring solutions not problems." This got hammered into me as a green engineer on a launch site where I asked my boss if I should do X or Y. He looked at me and said, "If you were the only engineer here what would you choose?" I said 'X' and explained why. He said, "great go do it" and I understood. Expand full comment Reply Share 3 more comments... Top Latest Discussions No posts Ready for more? [ ] Subscribe (c) 2024 Kent Beck Privacy [?] Terms [?] Collection notice Start WritingGet the app Substack is the home for great culture Share Copy link Facebook Email Notes More This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts