A recent article I read from Search Data Management examined data management best practices, specifically the importance of the data architect role. Traditionally, whoever is filling this position is responsible for ensuring a company's data assets are supported by systems that aid in achieving its goals. This is a big picture position.
The article asks the question, "Should data architects be an active participant in data management projects?" While this seems like a silly question to ask, the more you look at it, the more interesting it becomes.
If you are a small business with a single person in charge of data practices, there is a good chance that they are also the architect, so this question doesn't really apply. However, if your company has an IT team, more than one person will be making decisions.
Much like an architect for a building project, the data architect is focused on the big picture of how the entire data management system works and not day-to-day management. They design the building, but do not monitor the construction.
However, they do need to be brought into the fold about daily operations. If a new software solution is needed, the architect needs to know what the current struggles are that could be solved by a new system. This will allow them to make suggestions based on what options will both answer these challenges and integrate well with the rest of the solution.
To create a successful, efficient strategy for a data environment, organizations need to have a quality data architect in place. Your business's needs will determine how actively involved they are in your day-to-day operations.