Tim’s Weblog Tim's Weblog
Tim Strehle’s links and thoughts on Web apps, managing software development and Digital Asset Management, since 2002.

Stefan Tilkov: On Monoliths

Stefan Tilkov – On Monoliths:

“When a project is started, there is an assumption that it’s the goal of a project to create a single system. This typically goes unquestioned, even though the people or person coming up with the project boundaries often don’t decide this consciously.

[…] In my view, the most important thing to do, then, is to find out how many systems we should be building in the first place. It may be a single one, but it may also be two, five or a dozen (though probably not more) – clearly, the decision should be made very consciously, because whatever system boundaries you pick, you will likely be stuck with them for a very long time.”

Wed, 30 Oct 2013 09:44:30 +0000

Elegant Workflow: Interview with Chad Beer – Director, Digital Assets and Rights Management at American Express Publishing

Dave Ginsberg at Elegant Workflow – Interview with Chad Beer – Director, Digital Assets and Rights Management at American Express Publishing, and Part 2:

“I think search interfaces can be really, really klunky for something that should be so easy to drill down into, especially if you compare search on DAM systems to search on e-commerce sites. And ease of navigability in sort of a fluid, intuititive sense of how you get from one area of a DAM to another tends to be okay, but nothing that users can really teach themselves when you consider how much people can teach themselves about using apps on smartphones. There’s so much good interface design in the world now that is designed around guiding the user to using a new tool, where they don’t have to sit down and take a class. I just don’t see that kind of sweet user-sensitive design in DAMs.

[…] What I would tell anybody to do who’s getting a new system: Pick two to three primary goals they want their system to achieve, or pain points they want their system to address, and stick with those two or three. And don’t go any further – at least not until the system’s in place and successfully addressing that short list. […] People are disappointed by shaving it down. But then once it’s in place, people forget what you didn’t get. They only remember what it’s doing well, and if it addresses one or two or three things really well, people are happy. And you can build on that satisfaction and that success. You can prove your concept that way and then move forward with it.

[…] Having software at people’s fingertips teaches them so much about 1) what the software does well, 2) what they will absorb about the software and 3) what they really need from it. […] You can’t get to nuanced decisions until you’re actually touching software.”

Tue, 29 Oct 2013 11:55:14 +0000

Short links (2013-10-24)

Thu, 24 Oct 2013 20:07:51 +0000

Seth Gottlieb: CMS Adoption. Think Vertical, Not Horizontal.

Seth Gottlieb – CMS Adoption. Think Vertical, Not Horizontal.:

“High vertical adoption means using advanced features of the platform.

[…] Most of those flashy features that you see in a software demo are hardly used and the problem is getting worse, not better. […] I can’t tell you how many customer references I have talked to that only use the most basic features. And the software vendors are as concerned as I am about this. At least they should be. If vertical adoption doesn’t improve, customers will migrate to cheaper, simpler software.”

This applies to DAM software as well…

Wed, 16 Oct 2013 09:11:47 +0000

Naresh Sarwan: Can Current DAM Platforms Survive the Maturity Phase?

Naresh Sarwan – Can Current DAM Platforms Survive the Maturity Phase?:

“With a few notable exceptions, many DAM vendors have an almost limitless capacity for misplaced arrogance. They have incorrectly interpreted increased demand as a sign of improving customer satisfaction. This is a loud and clear message to vendors: just because you are selling well right now does not mean that users think your products are good enough!

[…] DAM vendors are falling over themselves to copy each other and building ever more complex platforms with layers of legacy issues that will need to be unwound and replaced repeatedly over the next few years. This will tie them up in knots and provide more agile competitors with an opportunity to make rapid progress at their expense.”

Wed, 09 Oct 2013 09:18:52 +0000

Paul Watson: Hack 70,000 UGC videos from the Storyful archive at MediaHackDay

Paul Watson – Hack 70,000 UGC videos from the Storyful archive at MediaHackDay:

“The value of one of the biggest assets that publishing houses hold, their content archives, has yet to be unlocked.

[…] What stories happening now have precursors in our archive?

[…] Finding new ways to search, tag, link, package and push data is vital to the evolution of the modern newsroom.”

I fully agree that there’s huge potential in archives. (Our DAM systems have always been both newspaper archival system and news agency content store. When selling, we’re intentionally downplaying the former part because money is made in newspaper production, not in archives.) The conviction that digital creations will have meaning and value later, often in unexpected ways, is at the very heart of Digital Asset Management. Why else spend money to keep yesterday’s stuff? Don’t forget about your archives and librarians!

Mon, 07 Oct 2013 21:13:00 +0000