craftcms.com Paid content

In business consulting, management means the ongoing work of planning, organizing, leading, and controlling a company's resources—people, money, processes, and technology—so the business meets its goals. It is different from consulting advice, which is outside expertise brought in to improve how that work is done. You need to understand management as a consulting topic when you are deciding whether a problem is a management gap (how the business is run) or a technical gap (a specific tool, system, or skill that is missing).

The four functions of management

Management is usually described through four functions. In a consulting context, each one becomes a place where an outside advisor can add value.

A consulting engagement often starts because one or more of these functions is not working well enough to support the business's goals.

Management vs. operations vs. consulting advice

These three are easy to confuse, but they sit in different places:

• Management is internal and continuous. It is the responsibility of the people who run the business every day.
• Operations is the execution layer—the day-to-day activities that deliver products or services. Management sets the direction; operations carries it out.
• Consulting advice is external and usually time-bound. A consultant does not take over management; they help management see problems, design solutions, and build the capability to sustain them.

A useful test: if the issue disappears when the consultant leaves, it was probably a technical fix. If it returns, it was likely a management issue that was never actually solved.

Core management areas a consulting client would recognize

When a consulting firm talks about management, it usually means some combination of these areas:

• Strategy — where the business is going and why
• People — who does what, how they are developed, and how decisions get made
• Processes — how work flows across teams and systems
• Performance — how results are measured and improved

Business transformation and IT strategy sit at the intersection of these areas. A transformation effort fails when it changes technology without changing how people plan, organize, lead, or measure. That is why management is often the real subject of a transformation project, even when the visible work looks technical.

Signs you need management help, not a technical fix

Use these signals to tell the difference before you hire anyone:

• The same problem keeps returning after each fix.
• Different teams have different answers to "what are we trying to achieve?"
• Decisions stall because no one is clearly accountable.
• Tools are in place but people are not using them consistently.
• Performance data exists but does not change anyone's behavior.

If several of these apply, the gap is likely in how the business is managed. If only one narrow system or skill is failing while everything around it works, a technical fix may be enough.

How this applies to choosing a consultant

When evaluating a consulting firm—such as one positioning itself around business transformation and IT strategy—ask what management functions they actually address. A firm that only implements systems is solving an organizing or controlling problem. A firm that also works on planning, leading, and performance is addressing management itself. Match the scope of the engagement to the scope of your problem, and expect the consultant to leave your team better able to manage without them.

Gourd craft is the practice of turning dried, hollowed gourds into decorative and functional objects—masks, musical instruments, bowls, and wall art. It works because a mature gourd dries into a hard, lightweight shell that can be cut, carved, burned, painted, and finished much like wood, while keeping the organic shape it grew into. The approach below reflects the range of work shown in the Elwha River Gourd Art galleries, which group pieces into wildlife, nature-inspired, human portrait, abstract, mask, and musical instrument categories.

Why gourds suit crafting

A gourd is the fruit of a hard-shelled vine in the Cucurbitaceae family, related to squash and pumpkins but grown for its shell rather than its flesh. Once cured, the shell becomes rigid and durable, and its hollow interior means a single gourd can become a container, a resonator, or a mask without being built up from flat material.

That combination—a pre-formed three-dimensional shape plus a workable surface—is what makes gourds attractive to crafters. You are not starting from a rectangular board; you are responding to a shape that already exists.

Core techniques

Most gourd work moves through a sequence of cleaning, marking, cutting, and surface treatment. The specific techniques vary by project:

• Cleaning and scraping — removing the outer skin and interior pulp and seeds after curing.
• Cutting and carving — opening the gourd with a small saw or craft knife, then refining edges with files and rotary tools.
• Pyrography — burning designs into the shell with a heated pen. The Elwha River site lists a separate pyrography section, and the same technique appears on paper as well as gourd surfaces.
• Painting, dyeing, and staining — adding color, often after sealing the surface.
• Assembling — combining a gourd body with other materials, which is how gourd banjos and thumb pianos (kalimba, mbira) are built.

A note on musical instruments

Gourd musical instruments are a distinct branch of the craft. The site's gallery includes gourd banjos and thumb pianos, where the dried shell acts as the resonator and the craftsperson adds a neck, strings, or metal tines. This is closer to instrument building than to decorative craft, and it requires the gourd to hold its shape under tension.

Types of finished pieces

The site also documents a "Making A Gourd Mask" page, which suggests mask-making is treated as a teachable process rather than a single finished product.

Preparing and drying gourds

The preparation stage is where most beginners lose a project, so it is worth treating as its own step:

1. Harvest at full maturity — the shell should be hard and the stem beginning to dry.
2. Cure in a dry, ventilated space — air movement matters more than heat; a damp gourd will rot or grow mold.
3. Wait until the gourd is light and the seeds rattle — this is the practical signal that moisture has left the shell.
4. Scrape and clean the surface — remove the outer skin and any mold, then sand.
5. Clean the interior — scoop out pulp and seeds before cutting openings or assembling parts.

Skipping the curing step is the most common failure point: an under-dried gourd will crack, shrink, or develop mold after you have already invested work in the surface design.

Where to find inspiration and community

The Elwha River Gourd Art site organizes its own work by subject and links outward to directories and web rings, including a gourd art directory, a general craft directory, and a crafters' catalog described as a virtual craft show running since 1998. These listings are a reasonable starting point for browsing other makers' work and for finding supply or exhibition channels.

The same site notes that its author, Patrick Loafman, has published a novel (Somewhere Upriver, Event Horizon Press) and two poetry chapbooks, and formerly edited The Dandelion Farm Review—a reminder that gourd craft often sits alongside other creative work rather than in isolation.

Practical starting point

If you want to try gourd craft, begin with a cured gourd, a small saw, sandpaper, and a rotary tool, and make a simple bowl or mask before attempting pyrography or an instrument. The skills transfer: cleaning and cutting teach you how the shell behaves, and that knowledge is what makes carving, burning, and assembly predictable later.

A CMS (content management system) is software that lets you create, store, edit, and publish content without hand-coding each page. You need one when more than one person publishes content regularly, when the same content has to appear in more than one place, or when you want to change how your site looks without rewriting the content itself. If you publish a single static page once and never touch it again, a CMS adds overhead you don't need.

The core problem a CMS solves

Without a CMS, every page is a file. Changing the headline on 50 articles means editing 50 files. Adding a byline format means touching every page again. A CMS separates the content from the presentation, so you write the article once and the system assembles the page around it.

That separation is the whole point. It means:

• Editors work in a writing interface, not in HTML.
• Designers change templates, and every page updates.
• The same article can feed a website, an app, and a print layout.

The main components

Most CMS platforms, including media-focused ones like BLOX Digital, are built from the same four parts.

A CMS that only does the first two is really just a writing tool. The value shows up in the last two.

CMS vs. website builder vs. DMP vs. VMS

These get confused because they overlap at the edges.

• Website builder — drag-and-drop page design, usually for a small fixed site. Weak on structured content, workflows, and multi-channel output.
• CMS — built around content items and their relationships. Better when you have many authors, many articles, and more than one destination.
• DMP (data management platform) — collects and organizes audience data. It doesn't publish content; it tells you who's reading it.
• VMS (video management system) — stores, transcodes, and delivers video. A CMS may embed a VMS, but they solve different problems.

BLOX Digital, for example, describes itself as covering CMS, digital publishing, advertising, engagement, and video management together — which is typical of platforms aimed at media organizations rather than general websites.

The choice depends on content type and channel

This is where most CMS evaluations go wrong. People compare feature lists instead of asking what they publish and where it has to go.

• Text-heavy news site — needs fast publishing, scheduling, taxonomy, and archive search.
• Broadcast or video-first — needs a VMS that integrates with the CMS, not a CMS with a video field.
• Print plus web — needs one content store that can output to both, or you'll retype everything.
• College or small media — needs low setup overhead and simple roles more than deep customization.

If your content lives in one channel and one format, a simple CMS is enough. The moment you add a second channel, integration between the CMS and the other tools becomes the deciding factor.

Practical criteria for evaluating a CMS

1. Ease of use for non-technical staff. Have an actual editor try to publish a story with an image and a scheduled time. Time it.
2. Scalability. Ask how the system handles a traffic spike and a content archive of tens of thousands of items.
3. Integrations. List the tools you already use — ad server, video, analytics, paywall — and confirm each one connects.
4. Cost model. Pricing is often subscription-based and quoted per organization, so ask directly rather than assuming. BLOX Digital, for instance, lists a "BLOX Pay" product and uses subscription language, but does not publish rates on the pages reviewed here.
5. Migration path. Ask what it takes to move your existing content in — and back out.

What to do next

Write down your content types, your publishing channels, and the number of people who touch a story before it goes live. That list, not a feature comparison, tells you whether you need a CMS at all and which category of platform fits. Then evaluate two or three options against the same list, using a real publishing task as the test.