We've all been there. You're on a web-based project, and things are going well. At least, you think they are. The right people are selected for the appropriate functions, and everybody's clear on their roles. You've got a designer, a developer, a project manager, and business stakeholders who are driving the requirements. You've got interlocked programs that tie in with your initiative, and you've got a fairly constrained budget to manage to. The timeline is tight, but if everybody just does their job, you should make your dates. The initial requirements are gathered, stakeholder expectations are set, and the first set of deliverables -- comps that define what the end product should (generally) look like -- is due. But it doesn't get delivered. The comps seem stuck in a perpetual working state with the designer, as repeat revisions are created behind the scenes in consultation with other designers... out of sight of the other stakeholders and app...
An ongoing conversation about how people's "Praxis" (the way they work in the world) intersects with others. Derived from the CycloPraxis work of Doug Johnson, this blog explores and applies an understanding of people's praxes to everyday workplace situations. From inter-organizational conflicts to intra-team tensions, from clashes that jeopardize a project's deliverable dates, to bad fits in positions, applying CycloPraxis understanding explains a whole lot. Let's talk about it!