Here are the questions asked:
- How are you involved with Digital Asset Management?
- How does a global organization focused on furniture and housewares use Digital Asset Management?
- What are the biggest challenges and successes you have seen with Digital Asset Management?
- What advice would like to give to DAM professionals and people aspiring to become DAM Professionals?
Henrik de Gyor: [0:01] This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Karl Lord, Lovisa
Idemyr and Tom De Ridder. How are you?
Lovisa Idemyr: [0:11] We’re good, thanks.
Tom De Ridder: [0:12] Good, thank you.
Karl Lord: [0:13] We’re very well, thank you.
Henrik: [0:14] How are you involved with Digital Asset Management?
Lovisa: [0:17] Karl and I, we’re working for Inter IKEA Systems, which is the franchise
store of IKEA so for us it’s really important to safeguard all the intellectual
property and the media assets. For me for instance, I’m involved because I was
a project leader for the first Digital Assets Management and rotation with it.
Since then I’ve been working with additional projects related to them and also
the questions that start to pop up once you go into this DAM business.
Karl: [0:44] I work on the IT side so I’m responsible for operations and securing
that the services within the company are working as they should so that the
business has the right availability for the DAM solution.
Tom: [0:56] I am the CTO of a company called Stylelabs and we’re based in
Brussels. We had startups, we started out as a WCMS company but we gradually
moved to the dark side. The back office for marketing solutions and then
DAM is our main thing right now.
Henrik: [1:15] How does a global organization focused on furniture and housewares
use Digital Asset Management?
Lovisa: [1:20] We use it for a lot, and we even have multiple DAMS with them
because we are so many different IKE A companies. We as a franchise to work
we need to protect the brand and also secure intellectual property. We are
making sure that the officially approved assets are available in our DAM so
that we can make additional usage of the assets, so that we can use it for local
marketing, etc. [1:46] We are using it both for the global marketing which is more
about the IKE A catalog, and so on. Then we’re also enabling local marketing activities
because the retailers can click the assets and make additional assets for,
let’s say additional artwork productions based upon that. So we kind of provide
the original assets that have the furniture design, everything is “hunky dory”
and good. Then they can further utilize the assets.
Karl: [2:15] We also use them in addition for the marketing purposes, we use a
lower resolution version for 3D for internal requirements for commercial planning
and store design. We build in 3D complete stores before they’re actually
in the world. The 3D products which we have in the assets as in the DAM will
be used, placing within a 3D model of the store. It’s for the building and design
of the stores and for the retailers. [2:41] So when we go out and deploy a new
store, we’ve already gone through and seen exactly what the flows are. The
passenger, the traffic requirements and so forth, and where the products and
volumes are necessary. Put that all in.
Henrik: [2:52] Excellent. What are the biggest challenges and successes you’ve
seen with Digital Asset Management?
Lovisa: [2:58] Well I would say that when we started this that we were kind of
a bit naive in terms of what DAM meant so it was kind of happily naive [laughs],
because we didn’t really understand what it would take from the business.
Everything from business to IT to infrastructure, and so on. We started off with
this great idea of having [laughs] the possibility to manage all the assets in a
nice way and being able to store and distribute that. [3:23] Then of course we
started a bit small having images, now 3D and product information. During this
roadmap basically getting to learn more about what is DAM all about, what are
the opportunities? A big help there has also been getting good support from
Stylelabs in terms of advising how can we use this technology in a way that fits
us. I would say that having good advisers, that has really helped us in that work.
Henrik: [3:51] Excellent.
Tom: [3:52] Generally speaking for Stylelabs, we’ve done other implementations
also. I can say that next to the technical challenges, the biggest challenge is
user adoption but it’s also the biggest reward. So if your community likes it then
the solution grows and you get back response which is great. So that’s the best
reward and the biggest challenge at the same time.
Lovisa: [4:14] For us for instance, we come from a quite scattered landscape,
having assets available at a dozen number of suppliers. So instead of people
having to find the right person at the right agency or production company, now
we actually know that we have at least one copy in our DAM, and we have a
good support organization for that. [4:38] It’s also a security from a corporate
point of view that all the assets are safeguarded, and it’s not so dependent on
only one person knowing who to call and so on. So that has been quite a reward
I would say because it’s actually working. People are more happy with getting
access to the assets and now it’s getting more popular also to talk about DAM
and intellectual property.
[5:04] Everyone is quite happy that the basics are in place because that’s the
biggest hurdle I would say, getting commitment, getting buy in, getting investments
and so on.
Henrik: [5:12] Of course.
Tom: [5:13] Doing it one step at a time is actually the way to overcome this. Take
it easy, the maturity of the client or the customer plays a big role in how much
we, as an integrator, allow in a first phase. We always try to say, take it easy because
big bang solutions are ready to fail. You shouldn’t try too much at once.
Henrik: [5:34] Makes sense. Baby steps.
Karl: [5:36] Yes.
Lovisa: [5:37] It is a lot to cope with in Germany, within IT, within business. So
many things that are popping up. So basically when you’re doing those kind
of questions, you have to drive additional question marks within the company
that no one has addressed so far. So you’re getting into taxonomy, archiving,
lifecycle management, you name it, search tags. [6:01] All the kind of things that
make sense to put together in a nice harmonized way but no one has really had
the chance to do that in the past. So I would say stepping into DAM that’s also
stepping into all those open, let’s say small silos. [laughs] Getting that into one
big you know [laughs] .
Henrik: [6:20] And what advice would you like to share with DAM professionals
and people aspiring to become DAM professionals.
Lovisa: [6:24] I would say, I went to one of the global DAM events four years
ago as a kind of “DAM for dummies” for me. It was totally new to me. That I
found really good because I got quite a broad input because you had the business
track, you had the technology track, and so on. Also being able to speak to
the people behind the project. Both the successful ones and also the failures.
Henrik: [6:49] Exactly.
Lovisa: [laughs] [6:50] Which was even more interesting. Basically getting to
know people, also being able to listen to, what were the pitfalls. Can we avoid
doing the same mistakes? Are there people there that can help us with certain,
let’s say parts that we cannot manage within our organization? So I think a kind
of mixture of trying to understand what you want to do. [7:13] Having good advisers
on board and having a good network of people that you can call and say,
“How do we manage this? How do you do that?”
Henrik: [7:21] Excellent.
Karl: [7:22] Yes, having that advisory board and being able to get that feedback
about the good and the bad. What’s good about being here now this time
around is that we’re now able to present our success and our discoveries back
and contribute now to the other people working with DAM. Having had the
access to the information now being able to contribute information back is a
Henrik: [7:44] Excellent.
Tom: [7:45] I think what’s interesting also in this DAM space is that it’s almost in
between marketing and IT. An impossible bridge to make most of the time but
that’s the beauty of it that you open up your eyes and you hear the stories from
both sides which I think is a rich experience for anybody to have.
Henrik: [8:08] Excellent.
Karl: [8:09] If you’re going into practical requirements, for example, I would say
preparation, preparation, and preparation to go into a project. Really know exactly
what exactly it is that you want to accomplish, and what the requirements
from the users are. Don’t just build a DAM because it’s cool to have DAM. If
there’s a need, use case, take that, establish and use that as your grounds for
Henrik: [8:30] Great points.
Lovisa: [8:31] I think also, in terms of a rise or looking into what we can gain
from it. I think not only calculating what does it cost or what do we gain, but
also say that it’s not really a choice, it’s really necessary. There isn’t really a, “No
we can’t do this.” So it’s more about saying, “What can we gain over time?”
[8:53] So there’s a basic implementation first, and then you can do anything to
gain leverage based upon that so the more you add, of course, the more return
on your investment you will get. It’s really nice to have the foundation in place
and now everything we add to that will just be beneficial to the business.
Henrik: [9:11] Excellent.
Tom: [9:12] I could add something about technology if you want. So technology-wise
I would advise to be open for anything and pick the best in breed of specific
use cases. Don’t try to go just with one silo big thing. Just open your eyes,
talk to a mixologist, and he or she will help you get your solution together.
Henrik: [9:37] Thank you.
Lovisa: [9:38] Thanks.
Karl: [9:38] Thank you.
Henrik: [9:39] For more on this and other Digital Asset Management topics, log
on to AnotherDAMblog.com. Another DAM Podcast is available on Audioboo
and iTunes. If you have any comments or questions please feel free to email me
at AnotherDAMblog@gmail.com. Thanks again.