Ethan Mollick's four guiding principles for using AI at work
Briefly

Ethan Mollick's four guiding principles for using AI at work
"A musician may begin learning a new piece and find themselves lost in the weeds, fumbling while thinking about fingering options, phrasing decisions, and micro-adjustments to dynamics. A golfer may end up actually lost in the weeds after needlessly obsessing over specialized techniques, swing plane, and ball flights. And the manager rolling out a new AI workflow? Their simple automation idea can devolve into scattershot attempts at broad goals, governance concerns, and vague existential questions about productivity."
"Instead of one mountain to climb, you can find yourself lost in a field of molehills, where a once simple objective has fractured into competing urgent-seeming priorities. When that happens, the smartest move is usually the least exciting one: step back and simplify. Remind yourself to ask targeted, simple questions. There's a reason musicians obsess over posture, timing, and scales. It's why golfers endlessly drill alignment, grip, and, yes, posture again. The basics aren't just "beginner material"; they're process checkpoints to use when recalibrating your efficacy."
People routinely overcomplicate tasks when learning or refining skills, allowing complexity to take over. Musicians can get lost in fingering, phrasing, and micro-adjustments while golfers obsess over specialized techniques, swing plane, and ball flight. Managers implementing AI workflows can see simple automation goals devolve into scattered priorities, governance worries, and vague productivity questions. A single objective can fragment into competing urgent-seeming tasks. The recommended response is to step back and simplify by asking targeted, simple questions and returning to fundamentals. Basics like posture, timing, scales, alignment, and grip serve as process checkpoints to recalibrate effectiveness. AI integration benefits from thoughtful, intentional application of fundamentals.
Read at Big Think
Unable to calculate read time
[
|
]