If you can’t remove yourself from architecture or design so that you can concentrate on managing the project, it’s time to choose. Either manage this project or become one of the technical staff. But don’t try to do both.
I'm not the only one to think that Architect and PM aren't playing well together.
In our research, we found that the most effective teams were skilled in all five styles, choosing the style that best fit the needs and goals of a project. For example, they might concurrently be involved in deep research on a User-Focused project, while relying on their experience for a Genius designed project, and spend a little time whipping out some one-shot functionality whose results would be Unintended Design.
Since the teams are working with different styles all the time, does it matter? Our research says it does. The teams that produced the best experiences knew these styles well and how to quickly switch between them. They knew when they needed to go whole hog and pull out all the stops for a User-Focused style project, while also knowing when it was important to bang out a quick design, knowing the results would essentially be unintended. Those teams had a rich toolbox of techniques and a solid understanding on how and when to use them.
There is no silver bullet.
Generally, in that group, there will be one or two loud voices. Maybe an Alpha Male or two. The important thing to note is that this is a small group. It will be difficult to reach common ground with a small amount of people.
ouch... that is my daily job.
Not a line I draw ends up on an end‑user screen. Not a word I write is compiled into code. Not a sentence I say instructs users. I draw, write and talk to enable the specialists I work with to excel at what they do and realise inspiring software for my clients.
I’m not a graphic designer, I am an interaction architect.
The NO!SPEC campaign: Serves as a vehicle to unite those who support the notion that spec work devalues the potential of design and ultimately does a disservice to the client.