Hmm. There isn't a deep philosophical objection to the notion of dependencies, but I think the easiest interface to a set of tasks and their dependencies would be a graph, and we've already built a tool for editing such graphs.
Would you mind if I reverse your question? I guess I'm not sure I understand what the objection is to using OmniPlan. We've designed OmniPlan to be very approachable, so you can quickly enter a list of tasks (in a simple outline) and then indicate their relationships by dragging between them on the graph. (You can ignore all the rest of the complexity in OmniPlan until you need it.)
I thought there might be an issue with using OmniPlan due to its cost (which would certainly be an understandable factor), but since you just indicated that your wife would never use it even if you did buy it perhaps I'm missing some other concern?
Would you mind if I reverse your question? I guess I'm not sure I understand what the objection is to using OmniPlan. We've designed OmniPlan to be very approachable, so you can quickly enter a list of tasks (in a simple outline) and then indicate their relationships by dragging between them on the graph. (You can ignore all the rest of the complexity in OmniPlan until you need it.)
I thought there might be an issue with using OmniPlan due to its cost (which would certainly be an understandable factor), but since you just indicated that your wife would never use it even if you did buy it perhaps I'm missing some other concern?