Structure looks different for everyone and varies from person to person, however this doesn’t mean that you there is no such thing as bad structure. The point of having structure is to better and more efficiently reach the ends to a mean.
Projects in general, especially in software development, have many different stages and steps that need to be managed. Having good structure specific to your own personal work method is mandatory to get something done. I personally benefit greatly from breaking things down in to their own specific containers which allows for easier mangement. If I’m building an application I might break down my tasks in to categories. From there I might find out which categories rely on other categories. From there I might order those categories in to levels of importance. Just by following a structure as simple as this allows me to build an application 100% faster than if I were to start picking tasks out at random.
Sometimes focusing on the process as oppose to what you need to get done is exactly what your project needs to get done. Structures can always be improved upon and and should regularly be examined in order to increase productivity. Some people operate best under what they would call less structure, which is totally valid because that in itself is a form of structure and is typically constantly being changed so rapidly that it might be better for these individuals to never even write or jot anything down.
I try to always think about how my structure works in building new tools and software and constantly iterate over it so that it can be allowed to evolve.