Differences

This shows you the differences between two versions of the page.

--- wiki:organization [2025/07/30 10:39] – esoeding
+++ wiki:organization [2025/07/30 13:13] (current) – esoeding
@@ Line 8: / Line 8: @@
 .1 gather information
-  *
   * Do overall research:
-  * What organizations exist in RDM,
+  * What organizations exist in RDM
-  * what is their goal? Do they have a clear goal? ist it commercial or community driven?
+    * what is their goal and overall strategy? Do they have a clear goal? ist it commercial or community driven?
-  * who funds them
+    * who funds them
-  * are they sustainable - will they still exist tomorrow?
+    * are they sustainable - will they still exist tomorrow?
-  * Which of them are relevant for you? Why?
+    * Which of them are relevant for you? Why?
+  * find use cases where similar problems have already been solved e.g. by an improved level of digitalization, organization, and/or cooperation.
@@ Line 33: / Line 34: @@
   * these steps need to be realistic
   * the steps should be aligned with overall global RDM practices or concepts.
-  * the steps may be depndant on each other. Take a look at the dependencies.
+  * the steps may be depndant on each other. Take a look at the dependencies
 .4 Prioritize the steps
@@ Line 42: / Line 43: @@
   * prioritize your steps again, based on resources and dependancies.
   * if by all means possible - don't invent anything new:
-  * - if you need tools - take a look if you can reuse existing tools
+  * - if you need tools or services - take a look if you can reuse existing tools
   * - if you need standards - make sure you can use existign standards
   * - if you need sematic concepts, make sure you use or add to existing vocabularies
-  * compile a list of criteria and metrics to decide, which tool / standard / vocablulary you want to implement
+  * - compile a list of criteria and metrics to decide, which tool / standard / vocablulary you want to implement
+  * always document what you indend to do, what you did and what use cases you implemented or discovered.
-.5 take a look atr your organization
+.5 take a look at your organization
   * RDM requires change management
+    * what kind of structure exists? Where are the advantages and disadvantages of the existing structures?
+    * what tools, services and procedures are already in use?
+    * Where do these structures support your strategy and where do they not support it?
+    * what steps have already been implemented, which standards are in use?
   * Do you have support by your center management? Do you have a mandate to implement or even suggest chages in RDM workflows?
-  * make a list of stakeholder, who shoudl be involved
+  * make a list of stakeholder, who should be involved
   * evaluate your stakeholders - who is critically necessary for the next steps, who can be adressed later?
   * evaluate your sub-organization (institutes, centers, labs) whic ones are more sisceptibel to iomplement changes workflows than others? Make a list of partners.
@@ Line 63: / Line 69: @@
   * look for partners, regional, national, international
   * who is in the same situation as you? How did they deal with the problem. Do they even have the same problem you have?
+.7. Some general recommendations
+  * be prepared with a consistant story of what you want to achieve
+  * Talk ands listen to your stakeholders. try to Understand their demand and pain-points
+  * Try to join or form networks of like-minded people on multiple levels: for general exchange across organizations, for implementation within an organization.
+  * Do not demand things, if you don't know how they fit into your overall goals
+  * As an organization - delegate a mandate, as a data manger, try to get a mandare from your organization.
+  * Explain what theis mandate means. It can mean to make changes to current procedurtes and workflows. Try to keep these cnages ans minimal invasive as possibele.
+  * do not build tools or services, without knowiong how to operate them long-term. Only build persistant reliable services, other wise they are prototypes and pilot studies. Build use-cases if they help to explain, what you want to do. Remember, that sustainable systems and workflows can not rely on protoypes and pilot projects.
+  * do not use terms or buzz-words where you don't understand how they fit into your overall concept. This in particular includes terms like knowledge graphs, ontologies, AI, machine learning, FAIR Digital Objects (FDOs) or alike.
+Finally: show leadership. don't order people what to do, but give them confidence, that what you expect them to do has been thoroughly thought through, is part of a larger master plan, and will not be revised or overturned in the near future. and it will benefit science and research as a whole.
+. Conclusion