Earlier today I was playing Cities Skylines, when I noticed that something was ablaze.
I don't know about the rest of us, but I don't consider a raging inferno to be part of the modus operandi.
Do you always have the same amount of steps and amount of information needed, or is there a chance that steps may be skipped, that parts of the step can be skipped, or that different responses can be given based on previously provided responses?
If the number of steps and sub-steps is fixed, the most sane approach would probably be to keep a series of Step#Tables and a master Process-table which links to the PK's of the rows of the individual steps. If it can all be dynamic, you're looking at some sort of questionnaire and you should adopt a table structure usually seen with those kinds of products. You might even want to consider using NoSQL if you feel that that approach better suits your model.
At work we use:
.NET 4.5.2 (C#, although I was tempted to write some VB.Net for shits and giggles), EPiServer, SQL Azure, Bootstrap, LESS, and jQuery.
Although I try to write new stuff without using jQuery as 90% of what we use it for (selectors and event handlers) can easily be replaced with browser native functionality.
Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.