Process vs. Problem Solving Mindsets

[kat]

Having just posted a tutorial (Unity FBX Model Import Rotation Fix) on a particular way to work with, or around, the problem of Unity constantly auto-rotating models despite being exported with the correct orientation axes (Y/up, Z/Forward), a couple of comments suggested the solution to this was simply a matter of "changing the export settings", the implication being the tutorial is wrong because its not explaining the "right" way to do something, rather than it outlining what to do when the "right" thing doesn't work.

This is the "process mindset" in action; it sees a problem and presumes it can be fixed by simply making sure the correct settings are used. For Unity model import, that's just making sure to set the axes correctly, because of course that's the problem.

Except, Unity uses a heuristic algorithm that analyses meshes during import beyond the XYZ axes values that, if it thinks a mesh is wrong, it will apply the coordinate fix to compensate, rotating the model on one or more axes, regardless (for Blender that's typically -90° around the X axis).

When this happens, the "process mindset" hits a wall because it can't comfortably step outside the problem. Instead, the it looks at the rotation settings and can't figure out what the problem is, largely because it doesn't understand the entirety of the process its locked in to, that the issue may be being caused by something outside their segmented understanding of the process itself - "it worked before, why isn't it working now?".

The "problem-solving mindset" sees the same problem - correct axes, failed import - and asks whether something else is going on, and whether there's another way to get to the same end result. Often this might not be the procedurally "correct" way to do something, getting models to behave correctly in Unity, but it'll work.

To the "process mindset" folks, this is a bad thing, because its not the correct thing, even though it works fine and produces the desired end result. And they will let everyone know.

For the "problem-solving mindset" they'll make a note of the problem and how it was solved so it can be used the next time the issue occurs. And they too, might let everyone know.

Both attitudes, or approaches, have their place; the "process mindset" tends to keep standards high or locked-in, whereas the "problem-solving" mindset remains flexible and keeps things moving when set processes don't work or match reality.

Learning to recognise the difference is a part of the craft no one really says anything about.

P.S. there's obviously a difference between "problem solving" and just throwing stuff at a wall to see what sticks.