A List Apart

Menu
Issue № 354

Get the most out of collaboration: in person and on paper.

Agreements = Expectations

by Greg Hoy18 Comments

Every client/vendor relationship is based on a set of expectations, whether they're stated or not. A lot can go unsaid or unspecified for any project, large and small. Not being specific can lead to disagreements, quarrels, and high blood pressure. But, it doesn't have to be this way. Greg Hoy says that while due diligence is important, being vague is a must. Yes, you read that right.

Facilitating Great Design

by Kevin M. Hoffman6 Comments

Imagine the most fulfilling, collaborative design meeting you've ever had. Hours seemed to fly by, and those hours were productive. Political and mental barriers melted away and in their place were innovative ideas, or realistic solutions for complex problems. For several shining moments the team worked as one; the conversation or the activity was equally fun and productive, and you left the room feeling smart and empowered. It's highly likely that someone in that meeting was a facilitator, either by design or by accident. Kevin M. Hoffman leads us through what it takes to facilitate great design.

More from A List Apart

Columnists

Matt Griffin on How We Work

Being Profitable

So you own a business. It’s the best job you’ve ever had, and it will be forever—as long as the business stays viable. That means understanding when it's profitable, and when you may have to make some adjustments. Don’t worry—it doesn’t require an accounting degree and it won’t turn you into a greedy industrialist.

From the Blog

Ten CSS One-Liners to Replace Native Apps

Håkon Wium Lie is the father of CSS, the CTO of Opera, and a pioneer advocate for web standards. Earlier this year, we published his blog post, “CSS Regions Considered Harmful.” When Håkon speaks, whether we always agree or not, we listen. Today, Håkon introduces CSS Figures and argues their case.

Longform Content with Craft Matrix

Jason Santa Maria recently shared some thoughts about pacing content, and my developer brain couldn’t help but think about how I’d go about building the examples he talked about. The one fool-proof way to achieve heavily art-directed layouts like those is to write the HTML by hand. The problem is that content managers are not always developers, and the code can get complex pretty quickly. That’s why we use content management systems—to give content managers easier and more powerful control over content.