Göke M. Frerichs

During my studies of Graphic Information Technology at Arizona State University, professors first spontaneously described me as a “Smart Digital Creative”. They used this to describe how I combined analytical-strategic thinking, digital-technical understanding, and creative problem-solving. It was a personal characterization of my working method, not an official university degree or a formal job title.

In the following years, I further developed this connection in my project work. Later, I consciously picked up the description again and made Smart Digital Creative the designation of my working method. This eventually led to the SDC method.

Today, this connection forms the basis of my work at goeke.digital. As a strategic sparring partner and external control level, I support digital development: I categorize tasks, justify priorities, and connect the contributions of management, subject matter experts, and implementation partners. My practical experience helps me to assess decisions with regard to their technical, communicative, and organizational consequences.

First, I am interested in how your company actually works. How does an inquiry arise? What questions do customers ask before making a decision? Where do employees repeatedly need the same information? Such observations are often more helpful than an early discussion about a specific tool. They show which digital improvement could make a comprehensible contribution in everyday life.

I combine this view with practical work on content, design, and technology. This allows me to assess recommendations also with regard to their implementation: What foundation is missing, how much coordination is necessary, and who will take over the later operation? The aim is to prepare a decision in such a way that the next steps become concrete.

You know your services and your company's conditions. I bring in the external perspective and my digital skills. If expertise from sales, product, service, or practice is required, it will be specifically included. Technical statements will be confirmed by the responsible persons. The responsibility for content and decisions should remain traceable.

An existing agency or an internal team does not need to be replaced for this. We clarify which role is already well-filled and where support is lacking. This can be occasional sparring, joint conception, or agreed-upon implementation by us. It is important that contributions and handovers fit together.

A conversation is helpful when a specific digital task is pending and you want to justify its next step. You don't need to prepare a complete service description for this. An example, an existing page, or a description of a recurring problem are sufficient for an initial assessment.

Openness to technical questions and realistic expectations are important for collaboration. Not every task requires an extensive project. If a limited correction is sufficient, the scope should also be oriented accordingly. The Collaboration page describes how it can become a concrete order.