What constitutes "skipping steps" or "making assumptions" depends on context and perspective. We can't allocate conscious attention to all of reality – reality is too big, complex and varied.

To interact productively, people need some common ground – some shared knowledge and perspective – which specifies what sorts of assumptions are inappropriate to make. Shared culture is crucial for this.

Existing cultural defaults are adequate for working as a cashier. But our culture doesn't prepare people well for intellectual discussions. It's maybe pretty close to adequate for intellectual discussions, but some adjustments are needed.

As a starting point, for intellectual discussion, people should assume less than they normally do. Don't skip over some things you'd normally assume and then see which ones are or aren't an issue. But people are bad at assuming less, bad at judging which of their assumptions are riskier, and bad at updating their future behavior according to information gathered like this.

An impasse is a reason (from the speaker’s pov (point of view)) that the discussion isn’t working.

Impasses take logical priority over continuing the discussion. It doesn’t make sense to keep talking about the original topic when someone thinks that isn’t working.

An impasse chain is an impasse about a discussion of an impasse. The first impasse, about the original topic, is impasse 1. If discussion of impasse 1 reaches an impasse, that’s impasse 2. If discussion of impasse 2 reaches an impasse, that’s impasse 3. And so on.

A chain of impasses is different than multiple separate impasses. In a chain, each link is attached to the previous link. By contrast, multiple separate impasses would be if someone gives several reasons that the original discussion isn’t working. Each of those impasses is about the original discussion, rather than being linked to each other.

When there is a chain of impasses, the most recent (highest number) impasse takes priority over the previous impasses. Impasse 2 is a reason, from the speaker’s pov, that discussion of impasse 1 isn’t working. Responding about impasse 1 at that point doesn’t make sense from his pov. It comes off as trying to ignore him and his pov.

Sometimes people try to solve a problem without saying what they’re doing. Instead of discussing an impasse, they try to continue the prior discussion but make changes to fix the problem. But they don’t acknowledge the problem existed, say what they’re doing to fix it, ask if that is acceptable from the other person’s pov, etc. From the pov of the person who brought up the impasse, this looks like being ignored because the person doesn’t communicate about the impasse and tries to continue the original topic. The behavior looks very similar to a person who thinks the impasse is stupid and wants to ignore it for that reason. And usually when people try to silently solve the problem, they don’t actually know enough about it (since they asked no clarifying questions) in order to get it right on the first try (even if they weren’t confusing the other person by not explaining what they were doing, usually their first guess at a solution to the impasse won’t work).

This non-communicated-problem-solving-attempt problem is visible when people respond at the wrong level of discussion. Call the original topic level 0, the first impasse level 1, the second impasse level 2, the third impasse level 3, and so on. If level 3 has been reached and then someone responds to level 2, 1 or 0, then they’re not addressing the current impasse. They either are ignoring the problem or trying to solve it without explaining what they’re doing. Similarly, if the current level is 1, and someone responds at level 0, they’re making this error.

The above is already explained, in different words with more explanation, in my article Debates and Impasse Chains.

It's very hard for people to learn by interacting with other people directly. Two major reasons:

1. Interaction triggers people to behave and interpret socially. They put most of their effort into social hierarchy stuff instead of learning.
2. People are complex and flawed. It's a lot to deal with in addition to the subject itself (the subject is e.g. philosophy or physics concepts). People have to deal with miscommunication, scheduling, mutual benefit, different background knowledge, being able to think about other points of view, etc.

School success does not imply being smart, wise or knowledgeable.

Failing your school classes or hating school does not imply lacking brainpower or lacking learning capacity.

Hating school doesn't mean you hate learning.

Enjoying school of getting A's does not mean you like learning or understand the topics covered in your classes.

These things aren't significant hints or clues. There isn't a strong correlation. You can't judge people by their relationship to school.

On the high end, if you're really great, that clashes with the conformity and obedience that school asks for. But being great can make up for it. If learning the material is easy for you, that advantage can lead to school success even if, e.g., you don't respect your teachers. It doesn't have to lead to good grades but it can; the result can go either way.

On the low end, if you're bad at thinking, that can lead to pretty good grades if you just do as you're told, make a visible effort, and have low starting points to improve from (teachers often give good grades for improvement instead of just for actual results).

If you fail a bunch of classes, it could be because you disliked them (with cause) and skipped classes or didn't pay attention. This can happen if you're smart or dumb or in the middle. There's stuff to dislike about class for everyone.

If you get bad grades, it could be because you saw how pointless it was to memorize things for a test and still not understand them. Maybe you didn't learn the material but at least you knew you didn't understand. Most people who pass don't understand the topics either, they're just e.g. more willing to pretend their confusions are successful learning.

If you get pretty good grades, you could be a stupid, obedient conformist. Or you could have seen lots of flaws in the system but been under extreme pressure from your parents to find a way to get pretty good grades anyway. Or many other things.

Don't judge people by how they did in school.

And especially don't judge yourself by how you did in school.

Project management is important for projects you do alone. Some people maybe think it's just for team projects. But by yourself it's still useful to have some idea of what tasks go into a project, estimate how long they'll take, estimate resource costs per task (e.g. how much money you'll have to spend), etc. Then you can look at your schedule and budget and see how long it'll take to get the project finished. And then you can consider: is it worth it compared to alternative projects?

A project merely means doing multiple activities/tasks over time which are meant to work together to achieve one or more goals. That's something people do alone or in informal, non-business settings. And it's something that can go wrong. There are plenty of ways to be disorganized and screw it up. So people have developed ways to better plan, evaluate and organize projects. But most people aren't taught them in school and don't go find out for themselves either, which makes their projects unnecessarily difficult and risky.

(In my opinion, the best project management author is Eliyahu Goldratt.)

Needing prerequisites for projects doesn't usually mean more school.

Schools broadly fail to teach much. They don't work anyway. And they teach a lot of the wrong things.

Let's take an example. You want to write a novel. What are some of the prerequisites?

You'll need to be literate and able to type (already done, no worries). You should be better at grammar. You also need to know about plotting, character development, and what existing novels are like (what are some good things that your novel should have? what are some flaws in prior novels that you want to improve on?). You'll also need some project management skills. You're going to spend maybe a year writing the novel (or maybe five years while working a day job?). How do you schedule and budget your time? How do you organize your efforts over many different days and months, so it all comes together into a completed project? How do you finish the project instead of stopping in the middle? How can you know in advance what projects you'll still want to do six months from now? I suggest you start with smaller projects and shorter writing before a whole novel.

So anyway, do you need school to learn grammar? You already went to school and still get lots of commas wrong! Lots of schools don't even bother trying to teach grammar. When they do teach it, it's often a bunch of memorizing arbitrary-seeming rules and teaching to the test (just like how they screw up teaching math).

It is important for a novelist to know how commas work. But the default, standard approach to learning that should be using books and the internet. Look there first before looking for a course let alone going back to school. Try to educate yourself and consider getting education from others (which usually doesn't work well at all) as a second option if self-education isn't working. (BTW, if you can't educate yourself, I don't know why you think some teacher is going to fix your problem for you and somehow make your learning work well.)

Also, schools pretty much don't even teach novel writing skills or project management skills until college. 13 years of K-12 education isn't enough to fit it in, apparently. Novel writing isn't a skill everyone needs so it makes sense not to teach it to everyone, but do people really need to wait until age 18 to start learning it?

And with project management the assumption seems to be that you don't need to know it because there will be a boss who knows it and you'll just follow orders. That's the life they are preparing you for by only even trying to teach project management at business school for people preparing to be bosses. And keep all your hobby projects small and short since you never learned how to manage a larger project! Project management is something pretty much everyone should know a bit about, but it's left out of general education at schools!

Learning to think rationally precedes learning to have rational discussions.

Discussion basically uses two skills: thinking and dealing with other people.

Language is part of thinking well. It'd be useful even if you were stuck on a desert island alone for the rest of your life. You should have practice and success using language in your thinking before trying to use language in discussions.

Looking at many sides of an issue is part of thinking well. You should be doing that alone. So discussion shouldn't be a big change where things go from one-sided to two-sided (or more). Discussion should involve people doing the many-sided thinking they would have done alone.

How can you figure out prerequisites you need? Look at your project plan. What steps are you planning to do? For each step, consider what skills and resources you need to accomplish it. Don't rely on getting lucky. Be reasonable.

For example, if a step is to build a log cabin, you should know how to do that. That means e.g. knowing cabin design and some woodworking skills. You'll also want a chainsaw and nearby trees. If a step is to trap wild animals and sell the furs, you should know what sort of traps to use, what animals are in the area, how to set the traps up, how often to check them, etc. If your plan is to spread ideas, you should know what the ideas say and why, why the ideas are superior to alternative ideas, and the answers to attempted criticisms of the ideas you're spreading.

What if you plan to learn as you go along? Knowing how to set a trap is a prerequisite for setting a trap. But you could do it in an earlier project step instead of before the project starts. That's often unwise because learning doesn't always go smoothly and it's hard to plan projects based around skills you don't yet understand (will you even like doing it?). Anyway, putting prerequisites earlier in the same project doesn't invalidate the concept of prerequisites.

It's also possible to divide a step into sub-steps and mix in learning prerequisites. You can split building a cabin into 20 steps, then watch a YouTube tutorial about the first of those steps, then do it, then watch a YouTube tutorial about the second of those steps, then do it, and so on. This is generally only a good idea with pretty simple, easy projects where success isn't very hard to come by and delays aren't a big deal (it especially works well with practice projects where learning is the main goal).