Another DAM Blog

Blog about Digital Asset Management


2 Comments

Launching first Kickstarter project related to Digital Asset Management: Transcribing Another DAM podcast

I launched the first Kickstarter project related to Digital Asset Management (DAM).

The Project

We need to fund Transcribing Another DAM podcast. Over 120 episodes of this podcast series including 80 interviews with different professionals from various organizations. The goal is to transcribe these podcast episodes from audio to searchable text.

How?

Kickstarter is a crowd funding site for projects. Someone posts a project with a defined end result. People back the projects they believe in. In this case, project involves transcribing the audio podcast episodes into text.

No, we are not going to ask you to transcribe the audio for us.

Transcription service will do all the transcribing of these podcast episodes and they charge for every minute of audio. There are hours of audio to be transcribed. This is why we need financial backing to pay for this work to be done and that is why I started this project to fund this effort.

Why?

Why do this? What is in it for you as a project backer? If you back this project with your funds and help make this project happen, you can get a reward depending on the amount you pledge. Aside from the rewards, you will be helping yourself and anyone interested in Digital Asset Management to have a full text version of most podcasts episodes, especially the 80 different interviews. These transcripts will be indexed and fully searchable so you can easily reference these podcasts and not have to take notes on what someone said. This also makes this more accessible to everyone for learning and enrichment of Digital Asset Management.

Rewards

If the project gets fully funded and we reach the goal of $3000, every backer who pledges at least US$20 to this project will get an ebook of all the transcriptions. The ebook will not be available to people who do not back this project. The ebook is a Kickstarter exclusive offer.

There are other very limited edition rewards offered. Check out the site for details.

Risks

If the project is not fully funded, does reach its goal, then nothing happens with the project. No transcriptions. No ebook. No rewards. All the money is reimbursed to backers. Move on to the next project.

I have taken in consideration that transcripts will need to be reviewed and that will take some time. There should be enough time to avoid delays in the timeline of delivering these transcripts and rewards by sometime in August. This will not be a rush job.

Am I done?

I am not finished creating more content and improving the site for users. Another DAM blog and Another DAM podcast will continue to exist. These will continue to be free of charge to access and reference for everyone.

I will continue creating more original content regularly since there is still plenty to talk about in the field of Digital Asset Management. There is plenty more to contribute and share. Some people who want this to go away, but I keep sharing more.

Are you ready to support these efforts of sharing more through this crowd funding effort?

Help support Transcribing Another DAM podcast at http://kck.st/YWTDPL


1 Comment

How do I create use cases for DAM?

A blog reader asked about how to create use cases for DAM.  I gave a presentation about this topic during a DAM conference.

What use cases did you have before DAM was part of the equation? Before you had a DAM, were your workflows documented?

All too often, use cases are not documented. In fact, they may be locked in multiple silos where each person (even within the same group ) do things differently.  Therefore, migrating to a workflow with DAM becomes a mystery. Without use cases, the user adoption of the DAM is often lower if users do not know why nor how nor when to use the DAM.   Where does DAM fit in the users’ daily workflow? Use cases can also affect the choice of a DAM solution.

Use cases need to be documented and shared.

Another reason for having use cases is training for new people. How do newly hired people find out how to do their job? Are they born with this knowledge? Should an employer expect everyone to know how to use all the tools and policies of the organization to get their job done?  Not likely.

Enter a new person (new hire) to the organization. What are they supposed to do? What tools are involved? When do they use the DAM and for what purposes?  Should new people operate differently than people doing the same tasks for years within the same organization? Not likely, but they often do. Does each person who coaches a new person give their own version of how to do things (plus or minus a few steps)? Is this standardized? This is often not only due to a particular level of experience, but lack of documentation and poor training. And we expect consistency. Somehow. Maybe by mind reading? That is not likely going to happen.

When you start researching a DAM for your organization, instead of looking at shiny features, see if it would work well with your use cases by presenting them to the vendor during a demo. Have real assets you would likely be working with along with real use cases. Ask the vendor to demo their solution for your use cases with your assets with metadata from start to finish in front of you.

Start building use cases with what you have and how you do things today.

  • What do you do today?
  • How do you do it?
  • Who does what?
  • When does it happen?
  • Why is it done that way?
  • What is the process?
  • What tools are used?
  • How could this improve?
  • How can this be done more consistently?

Be sure to consider the people, process and technology (in that order) which are involved from start to finish. Not sure who/how/what is involved? Ask by using…

  • Surveys
    • Online or paper form, with long answer questions, not simply ratings
    • All roles (don’t expect 100% return, even with a prize)
    • Send to everyone including decision makers and potential DAM users doing the daily work
  • Group workshops
    • Be aware of who is talking and who is not
    • Include all group members
    • In case extroverts have all the say while introverts remain quiet in the corner getting frustrated, have people take turns talking so everyone contributes
  • Individual interviews of:
    • Not just senior staff, but junior staff for a varying perspective
    • Both computer literate and those who prefer analog
    • All roles

When reviewing who is working, consider their role in the organization, not just their name so you can build and scale these job functions as needed.

Who makes the initial request? Who/What takes the request? Who handles/processes the request? Where does the request go after that? and after that? and after that? (note a pattern to fill the gaps)

How many other people do the same task(s)? Is this redundancy to handle volume or act as a backup? Can this scale up or down today based on the amount of work to do?

What is the volume of requests? Where do the requests get filled/completed? Who does this? Who/What delivers the end product/service?

Consider the whole life cycle of typical project from idea to delivery. And walk through all the steps.

How much communication is involved in all this? Likely not enough.  It is not enough to lock decision makers in a room. As discussed earlier, there are different points of view to keep in mind.

Keep the communication channels open among all differing points of view.

Stay positive. When negative points need focusing, laugh about it, then find a resolution.

Create roles. Envision the end result. Have a goal. Make it clear. Try even mind mapping. Simplify when in doubt. Follow through. Measure the results.

Avoid jargon and acronyms (so anyone can understand it). Be open to feedback, but have a schedule with deadlines and accountability.

However you create use cases, write them down and share it within your organization.

Let us know when you are ready for vendor neutral consulting on Digital Asset Management. We can also help you create your use cases.

How do you create use cases for DAM?