philosophy

Software for complex workflows can still be beautiful/simple/straightforward.

Beauty in software is primarily found in intuitiveness.

Software is best when delivered as frequently as possible in the smallest useful chunks.

Don't begrudge your users' working around your pristine workflow: workarounds are another way of clients describing how they'd actually like your software to behave, if you'd let them.

Listen to what your users and clients say, but always put yourself in position to understand what they (actually) do.

Share context: the why of a project is is not uniquely the domain of product. All contributors to projects will be more successful if they know who they are helping and how.

Be an open book: at any time, be able current project statuses, upcoming targets, and justification for efforts and allocation of resources.

Be lower-case "a" agile: if you learn something new about a workflow, something (even if it's just your understanding) should change, as soon as feasible.