Design (graphic and interaction), budgets, waterfalls, minimalism, and bridges to software developers

23 Jan 2009 - 11:29am
5 years ago
3 replies
953 reads
paul turner

1. Minimalistic UI design may suffice (I'm not convinced) for web content that are visited for a few minutes, but web applications that are stared at for hours need follow Gestalt principles. Graphic design is not about tossing comps over the transom and forcing downstream stakeholders to accept the consequences.

2. Will we return to waterfall approaches at companies that are eliminating or single-threading interaction design departments? That is say, will sneaky product managers go full bore, communicating all design ideas directly to software developers? Well, what choices will they have?
Circumventing interaction designers who strive to apply cognitive psychology, best practices, sensible peer-reviewed research, and to interpret user input (through contextual inquires, surveys, usability testing) is a sure way to undermine the promise of a vetted software application.

3. Except for let's say (I'm not sure how many) American companies, there are typically fewer than 5 interaction designers in design departments. They don't break the bank , and typically there are many more software developers.

4. WYSIWYG IDEs for designing user interfaces that produce code that can be imported into enterprise-level IDEs for software developers are sorely needed. I hope that some product fits the bill and that it goes into General Availability in the next 10 to 12 months.

Yours in the increments,

Paul Turner
Interaction designer


23 Jan 2009 - 1:12pm

Regarding #2, as a Product Manager I like to use everyone that's available to create great products - including Interaction Designers. Unless your Product Manager is in the wrong job and actually wants to be an interaction designer or their boss pulled their budget (and their staff) such that they had to play the role themselves, then there's no reason the Product Manager should circumvent the Interaction Designer. Interaction Designers add great value. I'm glad to have them on the team and would want to leverage their contributions and abilities.

23 Jan 2009 - 4:01pm
Samantha LeVan

Product managers have a strong grasp of market trends and make it a
point to understand the demographics and buying power of their
customers. In organizations that can't afford interactions
designers, supporting product managers with design training and
exposure to interaction designers can work as a temporary solution
until designers are hired, though cannot become a permanent

I have also seen friends and colleagues in IA and UX roles transition
to product management positions for job stability and because they
have grown a desire to drive the business aspect of the design. In
small organizations, this might be a good way for design to remain
with designers in a tight budget environment.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new

23 Jan 2009 - 8:39pm
Angel Marquez

I am curious to how a product like this manifests:
Sofatronic's kaleidoscope <> uses
the eclipse <> IDE and addresses the BD-J

The product addresses all facets of the dev cycle. If a team was clever
enough to use them to their advantage and use the QA tracking system
integrated with the PM milestones the pre-production-post is manageable from
one app.

I am curious if the people that make the products I find useful,like this
one, follow the 'rules'.

1. Do these guys even have interaction designers and project managers?
2. Are they stringent in their development process?

How did they take what is my obvious want and need and package it just the
way I wanted it?

The support was accommodating as well.

Syndicate content Get the feed