What Debra Wilson Skelton's Method Actually Looks Like in Practice
The systematic method for creative thinking that Debra Wilson Skelton unpacked isn't a magic framework you apply once and get genius results. It's more like a set of constraints you put on yourself so your brain stops wandering into unproductive loops. I spent about eight months working with this during a content strategy overhaul at a mid-size agency. We were burning through brainstorming sessions with zero output. Nothing stuck. People had ideas, but they were always the same five ideas dressed in different words. Skelton's approach breaks creative thinking into phases: divergence, structured filtering, and convergence with documentation. The divergence phase is where most teams fail. You're supposed to generate without judgment for a set window. Fifteen minutes. No editing. Just output. I've seen people try to rush through this in five minutes and then wonder why their ideas feel thin. The structure comes after. That's the filtering phase, where you apply specific criteria to eliminate or combine concepts.
The Ups And Downs Of Creative Thinking With Debra Wilson Skelton Unpacking The Systematic Method
Here's how the method actually runs day to day. You start with a problem statement written on a whiteboard or doc. Not a question. A statement. "Our onboarding email sequence has a 40% open rate but 8% click-through." Specific. Measurable. Then you enter divergence mode. Set a timer. Write every possible angle you can think of. Bad ones included. Ugly ones. The point is volume, not quality. I learned this the hard way during a campaign project where my team kept self-editing mid-generation and ended up with three similar email subject lines instead of thirty raw options to work from. After divergence, you move to filtering. Skelton recommends using a simple matrix: impact versus feasibility. Score each idea on a one to five scale for both axes. This sounds basic but it catches things you'd otherwise miss. An idea might feel brilliant emotionally but score a two on feasibility because it requires engineering work you don't have bandwidth for. Or vice versa. High feasibility, low impact, which means it's safe but forgettable. The convergence phase is where you take the top three to five ideas from the matrix and develop them further. This is where you actually produce usable output. Concepts become drafts. Drafts become tests. Tests become data. The whole cycle from problem statement to first testable asset usually takes me about ninety minutes if the team is coordinated. Longer if someone decides to rewrite the problem statement halfway through, which happens more often than it should.
One edge case that trips people up regularly: this method struggles with ambiguity-heavy problems where the problem statement itself isn't clear. I ran into this when a client asked us to "rethink our brand voice." There was no metric. No concrete pain point. The divergence phase produced pages of generic adjectives. We wasted two sessions on that before I reframed the problem as "our social captions aren't driving engagement compared to three competitor accounts, and we need to identify the specific tonal gap." Suddenly the method worked because the constraint was real. Another nuance beginners miss: the filtering matrix isn't static. You can adjust the weightings depending on what matters. If you're a startup with limited resources, feasibility might count double. If you're an established company with budget to burn, impact carries more weight. The framework bends to your context. It's not dogma. There are real downsides though. The biggest one is that it doesn't work well for purely intuitive or aesthetic creative work. If you're designing a logo or composing music, the structured filtering phase can actually degrade the quality of the output. You start optimizing for spreadsheet scores instead of feel. I've watched designers shut down creatively when forced through this method because the process replaced instinct with analysis paralysis.
Get the Full Details
Another limitation: it assumes you have a team willing to sit through the full process. Solo creators sometimes find the documentation overhead drains creative momentum. The act of scoring and categorizing every idea can feel like busywork. There's a middle ground where you do the divergence and filtering internally in your head and only write down the final selections. That cuts the time in half with minimal loss of structure. If you want to try this, the core materials Skelton references are available through her published frameworks on creative strategy. The basic matrix template is simple enough to build yourself in thirty seconds. Impact on one axis, feasibility on the other, ideas in the cells. Score them. Move the high scorers forward. That's it. The method won't fix bad problem statements or teams that don't trust the process enough to generate truly wild ideas during divergence. But for structured creative work with clear objectives, it removes the guessing game that usually slows projects down. I use it now as a default whenever a creative brief comes in with measurable goals. For everything else, I fall back on something looser. That's been working well enough.
