I am often wrong

verdverm

sorry, but when you reach certain levels of influence, you need to slow down, be more methodical, and not be so flippant

glimshe

Nothing more annoying than a manager with a personal know-it-all framework requiring people to follow it or else they get "feedback".

cube00

I can't say I agree with forcing your team to use your own personal "framework" of approaching a problem or else you'll get "feedback". > Sometimes I will give feedback to people when they are missing steps in the framework, or are poorly executing some of the steps. I expect the same feedback in return. I also don't like that urgency is built in as the standard process either, no wonder everyone is burnt out. > 6. Act with urgency to achieve the goal

otterley

This seems strongly aligned with the Amazon doc-writing and decision making process. I found it to be unusually effective as a business process, and took it with me when I left to my current role. Making thoroughly informed decisions and iterating on a decision doc before committing to a direction and plan is better than every alternative I’ve ever observed in my career. The criticism I’ve read thus far on this thread seems unwarranted. I give the same kind of feedback to my mentees when their work product or process could use improvement.

0gs

i am pretty sure it would just be "wrong," not "meta-wrong," and given the title, i am giving myself the point.

Avicebron

7. Reflect on that goal?

well_ackshually

I, I, I, I, I, I, I, Me me me me me me This is what happens when you let things get to your head. You work on a (highly inefficient, often broken) piece of extremely basic software by prompting a slot machine and hoping it works. Calm down and stop forcing your shitty framework on employees, you're the most replaceable cog of all.

6LLvveMx2koXfwn

Unlike me, 56 and yet to be wrong once.

Imanari

Steps 1–5 of his framework are increasingly formal ways of saying “figure out what’s going on before doing something,” followed by step 6: “then do it fast”

jascha_eng

That's what it took to finally support Agents.md I guess. Boris had to blog about having made a mistake. How about you stop taking things so personal instead and let others steer more.

ks2048

> I love being wrong I prefer being right, but to each their own.

someguy101010

a foolish consistency is the hobgoblin of little minds

atoav

Yeah? A very basic process, most people use some variation of this implicitly without talking about it. This sounds like a slightly narcissistic manager who thinks people are doing it wrong if they don't act like small copies of him. There are multiple ways to reach the same outcome and a lot depends on your information. E.g. I typically have a mental model of a system in my head, meaning when some problem needs fixing very likely I already know where it would need fixing and already think about the various future implications arising from a different fix. A point that is totally absent from that framework. Being a senior dev myself I have seen enough good software turn bad to know that seemingly innocent technological decisions can come with huge and lasting implications. The fact that this is missing here is speaking volumes about the lack of experience at display here. Your task as a manager isn't to create small copies of yourself. Your task is to know each persons weaknesses and strengths and compose the work in such chunks that the weaknesses have little effect, while the strengths multiply. For this you will first of all have to trust your people and lead them to discover certain ideas themselves. E.g. if you feel someone always jumps gun-ho I to the task without doing the research, just tell them to give you the research first. Do that a few times and they might realize how useful that is.

121789

The most annoying thing about this is that the steps are out of order unless the definition of problems and goals are intermixed 1. define a goal 2. understand information and gaps in information 3. define and prioritize the problems to achieve that goal 4. identify potential solutions for top problems and prioritize 5. measure success and do all of it with urgency (magically managers want everything done with urgency)

badgersnake

“I am often wrong” is directly from how to make friends and influence people.

brcmthrowaway

Just retire at this point, you don't even have to work.

infamia

> Something that people learn quickly when they work with me is that my approach to pretty much every problem is: > ... > 6. Act with urgency to achieve the goal If everything is urgent, then nothing is. This guy sounds miserable to work for and with. Assuming this is accurate and not just hyperbole, he is essentially saying he has no prioritization skills because everything is urgent. I think most people who have been around the block have worked with people like this, and unbeknownst to them, their coworkers develop a default snooze button associated with most of their requests and projects.

fjni

> I hope it is interesting or helpful I think you're wrong. I think it's embarrassing. Though I might be wrong.

preommr

And yet there's none of this uncertainty or caution with his posts that then go on to have massive ripple effects because of his position at Anthropic and the marketting related to claude. I personally have a lot of anger and frustration with many people in the ai hypesphere that are just mindlessly frolicking around without a care in the world, happy to speak into the megaphone offered by masses that are in a rat-race to avoid some AI dystopian hellscape that keep getting painted by these thought leaders... and then going "oopsies... I am just human guys... y so mad?!"

glitchc

This guy doesn't think deeply about any problem, possibly because he has never had to and probably because he has never wanted to. He would probably make a good residential plumber.