Choosing a Workshop Pace That Protects Process Over Product

Last spring, I watched a ceramics instructor tell a student—mid-coil, hands covered in slip—that her pot was taking too long. 'Just finish it,' he said. 'We need to fire by Friday.' The student looked at her lumpy, lopsided vessel. She pinched it into a quick bowl shape, skipped the texture she'd planned, and handed it over. The piece came out of the kiln looking like every other beginner bowl. She never took another workshop.

That moment stuck with me because it wasn't malicious. It was a pace problem. The instructor was up against a firing schedule, a rental clock, and a syllabus. He chose product over process. And the student lost something—maybe the desire to try again. Choosing a workshop pace that protects process isn't just about being slow. It's about making deliberate decisions on when to push and when to let go. This article walks through how you can do that without burning the kiln down.

Where This Actually Bites: Real Workshop Scenarios

The weekend watercolor crash

Twenty-two adults, brand-new brushes, a studio flooded with north light. The instructor—a lovely painter whose landscapes I'd admired—announced we'd finish two complete pieces by Sunday evening. By Saturday afternoon, half the class had abandoned their first attempt. The problem wasn't skill. It was the beat. She demoed wet-on-wet for eight minutes, then walked the room correcting our results. No pause for us to watch the pigment bloom, no moment to sit with the mess. One woman beside me kept layering color over half-dry paper, chasing a shape the instructor had already moved past. She cried in the parking lot. Not because she couldn't paint—because the pace told her she couldn't think. The workshop ended with eighteen barely-dry paintings, zero conversations about what anyone actually wanted to say.

— retired art teacher, Michigan workshop

That sounds extreme. It's not. I have seen this pattern repeat across disciplines—the instructor confuses coverage with learning. The catch is that watercolor unforgivingly punishes speed: once it's down, it's down. But the real casualty was quieter. Nobody risked a bold stroke. Why would you? There was no room to fail.

The all-day coding sprint that produced nothing

Five developers, one borrowed conference room, whiteboards wiped clean every ninety minutes. The brief: build a creative tool prototype—something playful, glitchy, expressive. By hour three, the team had scrapped two architectures. By lunch, the lead had taken over the keyboard. Sympathetic, but deadly. A sprint mentality treats thinking as overhead, so the group optimized for output: lines of code, commits, a demo that sort-of-runs. What actually surfaced? Nothing original. They built a weak clone of something they already knew. The pace demanded working over weird, and weird is where creative tools come from. One participant told me afterward, "I had an idea about drawing with sound data. I never even mentioned it." That sound-data idea? It would have taken three hours to prototype. Four, with detours. The schedule couldn't absorb detours. So it died—not from complexity, but from a pace that punished the detour itself.

The tricky bit is that nobody was lazy. They were efficient. Wrong target, efficient aim—still misses.

The writing workshop where feedback killed voice

Eight pieces of fiction, four hours, one rule: everyone reads first, then critique. The facilitator, well-meaning, used a timer. Two minutes praise, three minutes suggestion, move on. First story got cautious notes about sentence rhythm. Second one got the same. By the fourth, participants had developed a feedback script—tighten the pacing, watch the adverbs, show don't tell. Sound advice. Also completely context-blind. The seventh story was a fragmented, feverish piece about grief. The writer used sentence fragments deliberately, broke grammar on purpose. The timer couldn't distinguish between bad craft and risky craft. So the group "fixed" it. Two weeks later, I heard that writer had stopped sharing drafts entirely. The pace of feedback—uniform, compressed, mechanical—had trained her to produce acceptable sentences instead of honest ones. That's the real wound: when pace prioritizes product, voice gets flattened into something publishable and dead.

We fixed this later by letting the writer decide the feedback order. Slow down for the strange stuff. Rush the plain stuff. That one change—five minutes of rethinking—saved the room.

What People Get Wrong About Process vs. Product

Time constraints vs. pressure: not the same thing

The most persistent confusion I see in workshops is treating every deadline as an emergency. A time constraint is just a container—it says 'we finish at 4pm.' Pressure is the feeling that if you don't finish the drawing by 4pm, you've wasted everyone's afternoon. Those are different things, but instructors collapse them constantly. The clock is not inherently the enemy; the anxiety we pile onto it's. I've run three-hour sessions where people finished early because they felt allowed to work at their own rhythm within the block. Meanwhile, a ninety-minute class with no stated permission to slow down produces panicked scribbles and half-dried glue. The catch is subtle: you can say 'we have two hours' without adding 'so hurry up.' Most people don't know they're adding that second sentence. They just radiate tension, and the room absorbs it.

What usually breaks first is the student's willingness to scrap something that isn't working. Under pure time constraint, a potter might set aside a lopsided bowl and throw a second one. Under pressure, they desperately try to fix the lopsided bowl until the clay is a soupy mess. The timeline itself didn't cause that—the perceived judgment did. Quick reality check: when you watch master craftspeople demonstrate, they often work fast. But they also abandon pieces mid-way without a flinch. That's the difference between speed as fluency and speed as fear.

Process isn't just 'going slow'

Another misfire: people hear 'protect the process' and imagine everyone moving at a glacial, meditative pace. Wrong order. Process is about the sequence of decisions, not the speedometer reading. A watercolor workshop can move briskly through five practice washes if each one is a clean experiment—dip, stroke, observe, discard. That's fast process. A 'slow' session where the instructor repeats the same instruction three times because nobody understands the brush angle? That's drag, not depth. Process protects the logic of making, not the pace of the clock hand.

I once watched a ceramics instructor let students wedge clay for forty-five minutes—tedious, physical, repetitive. New students hated it. 'We're wasting time,' one muttered. Then she asked them to throw a cylinder. Every single one held shape on the first pull. That wasn't slow teaching; it was front-loaded process. The mistake people make is thinking 'process' means endless meandering or touchy-feeling check-ins. It doesn't. Process means you know what step comes next, and you don't skip it because you're impatient to see the finished object. That can take ten minutes or two hours. The number is irrelevant; the sequence fidelity is everything.

'The fastest route to a finished piece is often the one with the most detours—if you're learning on every wrong turn.'

— overheard at a letterpress workshop, after the third jammed platen

Product isn't evil; it's a horizon

Somewhere along the way, the anti-product crowd turned the finish line into a villain. That's a mistake. Having a clear outcome—a glazed mug, a printed zine, a staged scene—gives the process its shape. Without a horizon, you're just wandering. The problem isn't wanting a product. It's treating the product as the only validator of the time spent. That shift is tiny and toxic: 'I want to make a mug' becomes 'if this mug is ugly, the whole class failed.' The mug is a target, not a judge. You can aim for it without worshipping it.

We fixed this in our cyanotype workshops by framing the final print as 'a record of your decisions,' not 'the success or failure of your afternoon.' Same end result—a blue photograph on cotton—but the emotional weight changes completely. Students stop comparing their exposure times to their neighbor's. They start talking about why they chose a particular leaf arrangement. The product still exists. It just isn't the stormtrooper in charge. The trade-off here is counterintuitive: when you demote the product from verdict to souvenir, the actual quality of finished work goes up. People risk more interesting compositions. They stop playing safe because they're no longer terrified of the critique that waits at the end.

The horizon metaphor matters: you steer toward it, but you don't have to stand on it. Most workshops that get the pace right keep an image of the finished thing visible—they show examples, they describe success criteria—but they never demand that every student's version match that image exactly. That gap, between 'this is what we're making' and 'you must make it look like this,' is where pacing freedom lives. Ignore the gap and you're back in rush mode. Name it explicitly and suddenly people know when to push forward and when to pause. The horizon tells you direction. The path underneath your feet tells you speed.

Pacing Patterns That Actually Work

The 80-20 Rule for Timed Exploration

Most workshops collapse under a simple math error: instructors estimate every step as if there's infinite slack. Then panic hits at minute 45. The fix is brutal but liberating—reserve 80% of your total time for the part students actually struggle with, and condense instruction, materials handouts, and cleanup into the remaining 20%. Yes, that means your beautiful demo gets three minutes instead of twelve. That hurts. But I have watched students freeze during a complex glaze application because the teacher spent twenty minutes showing off her own technique and left four minutes for the class to try theirs. Wrong order. The 80-20 split forces a radical priority: what do they need to do versus what do they need to see?

The catch is that most instructors resist because it feels stingy on content. But content that nobody executes is museum signage, not learning. We fixed this once by running a textile workshop where the scheduled 'explanation of resist methods' took exactly seven minutes—slides, one live pass, done. Then the group spent fifty-two minutes failing gloriously with wax and dye. The seam blew out on two pieces, one student dyed her sleeve, and everybody left with a visceral understanding of crackle effects that no lecture could buy. That's process. That's what the 80-20 rule actually protects.

Two-Speed Workshops: Fast Drafts, Slow Refinement

Here's a pacing pattern that sounds crazy but works: push students through a rough version of the entire project inside the first quarter of the session. Messy, incomplete, ugly—fine. Then stop. The second phase moves at half speed, sometimes slower, with deep revision. The psychological shift matters more than the logistics; once they've seen the whole arc, perfectionism stops strangling curiosity. I have seen ceramic students spend forty minutes smoothing a single pot rim during the first pass, then run out of time to even attempt the glaze. That's the product-mindset trap baked into single-speed workshops.

Two-speed workshops flip the script. The fast draft phase is explicitly permission to produce garbage. 'Your first handle will wobble. Good. Make it wobble faster.' Then the slow refinement phase becomes a genuine problem-solving session, not a race to the finish. The tricky bit is that instructors must enforce the timer for the fast phase ruthlessly—no extensions, no 'just five more minutes.' One workshop I ran on linocut prints, the fast draft clock hit zero, and I physically collected everyone's half-carved blocks. Protest erupted. Then the slow phase started, and those same people spent forty minutes studying each other's crude first passes, stealing ideas, and deciding what to actually keep. That timing created collaboration. A linear pace never does.

Embedded Milestones That Don't Rush

Milestones usually act as pressure valves—hit this mark or fall behind. But process-protecting workshops invert them, using milestones as permission to pause. Instead of 'complete step three by 2:30 PM,' the milestone reads 'by 2:30 PM, stop and notice what's frustrating you.' Different animal entirely. The rhythm becomes: do, reflect, adjust, repeat. Reflection isn't a luxury add-on; it's the structural backbone that prevents the default rush toward the finished object. I've seen woodworking students hit a milestone, realize their joint fit is off by two millimeters, and stop to re-cut instead of forcing it. That's the whole point.

'We spent ten minutes staring at failed seams. That was the best ten minutes of the class—everyone saw how the material actually behaves, not how we wished it would.'

— workshop leader, community print studio

The anti-pattern is obvious in retrospect: most milestones are just disguised deadlines. They measure compliance, not discovery. A process-protecting milestone asks 'What did this step teach you?' instead of 'Did you finish it?' One practical trick—embed a 'show and tell failure' checkpoint at the 40% mark. Each person holds up their busted prototype, explains what broke, and gets a round of applause. That single moment resets the entire room's relationship with imperfection. It's cheap. It takes maybe eight minutes. And it kills the rush-cycle dead because nobody wants to rush toward a public confessional of shoddy work. The pace slows organically after that, not because of a rule, but because the workshop's culture just shifted.

Try this next week: pick any three-hour workshop you run or teach. Carve out the middle thirty minutes for nothing but unstructured failure discussion. No instruction. No troubleshooting. Just 'here's what I broke and why I'm glad.' See if the final hour doesn't produce better work than the entire session usually does.

Anti-Patterns: Why Instructors Default to Rush Mode

The 'Finish Line' Fallacy

Most instructors set a finish line and then race toward it. Wrong order. The finish line should be the horizon, not a wall you hit with your face. I have watched a master potter refuse to throw the last three pieces in a session—right when students peaked—because the mental rush of 'finishing' collapses technique into frantic motion. The fallacy assumes completion equals success. It doesn't. Completion that destroys the builder's confidence is a net loss. The real product is the person leaving the room wanting more, not the misshapen bowl that made them hate clay.

The toxic logic goes like this: if we finish all planned pieces, the workshop was worth the money. That sounds fine until you see a student's last object crater in quality because they skipped a critical centering step. The catch is—students don't blame the pace; they blame themselves. 'I'm just not good at this.' No, you were just rushed. By the time the instructor realizes the cost, everyone is exhausted and the feedback loop is a graveyard of half-corrected mistakes.

Panic Pacing When the Syllabus Is Too Full

You packed six activities into a three-hour slot. Three hours is really two hours and forty minutes after setup and cleanup. So you panic. You clip demonstrations, skip one troubleshooting walk, and tell a student 'we'll fix that at the end.' But ends don't fix anything—they amplify flaws. The syllabus is the anti-pattern's best friend: it gives permission to ignore the room's actual rhythm. I have run a linocut workshop where I dropped an entire second layer to recover breathing room. The prints were simpler. The students smiled. Their next three pieces at home were better than anything they would have produced under the original plan. The syllabus lied to me; the students told the truth.

Quick reality check—projects survive cuts. Relationships with messy beginners don't. When you watch the clock and sprint through the 'how to fix a tear' demo, you're trading future independence for current coverage. That trade fails every time. The moment a student's paper rips later, they have no internal repair script. You saved five minutes. You lost a month of their willingness to try again.

Why 'Just One More Piece' Feedback Loops Fail

'One more piece—just to lock in the motion. You'll get it this time.'

— Instructor who lost the room, ceramics studio, 2023

That phrase sounds generous. It's not. 'Just one more' extends the same flaw pattern without intervention. The student throws another wobbly cylinder. The instructor corrects the same wrist angle. Repeat. The only thing that solidifies is frustration. The anti-pattern here is mistaking volume for mastery. Pushing for an extra piece when the student is mentally fatigued doesn't build muscle memory—it builds sloppy habits. I learned this the hard way in a life-drawing session: instead of letting people redraw a failed gesture for the seventh time, I stopped them, walked them through a ten-second breathing reset, and asked them to draw only the negative space. That single shift in attention fixed more than six rushed attempts had.

The deeper issue? Instructors default to rush mode because they're afraid of silence. Afraid that slowing down looks like incompetence. That students will complain the class was 'too easy' or 'not enough content.' But the room feels the difference between a teacher who trusts process and one who is filling time with frantic production. Your job is not to maximize output. It's to protect the emotional bandwidth that makes good output possible. The next time you feel the pull toward 'one more,' pause. Ask yourself: am I teaching, or am I hiding my own anxiety behind a wet wheel?

Long-Term Costs of Getting Pace Wrong

Burnout and Drop-Off—the Silent Workshop Killer

The first thing that breaks isn't the curriculum. It's the people. I've watched a dozen morning workshops where the instructor, panicked about time, starts handing out pre-sliced materials halfway through. Students don't finish their pieces, but they do finish frustrated. That student who loved the first session? They don't re-enroll. Not because the craft was hard—because the experience felt like an assembly line. Returning students are the lifeblood of any serious workshop. Lose them, and you're constantly feeding new rookies into a leaky bucket. Worse, the ones who stay model rushed behavior: they stop experimenting, stop asking questions, and learn to produce fast but shallow work. That's a cultural infection, not a hiccup.

'We finished early, but three people never came back. I thought speed was a compliment. It wasn't.'

— ceramic instructor, after a 'fast-fire' glaze workshop

The catch is that drop-off won't show up in your end-of-session smiley-sheet surveys. It shows up three months later, when registration dips and nobody can name why. You trade an A for the class photo for a C in long-term loyalty.

Shallow Learning That Doesn't Stick

Pushing for a finished product every session carves neural grooves that are fast—and brittle. Students learn the sequence of steps but not the why behind any of them. Quick reality check: if you rush a novice through wet- felting and they produce a lumpy scarf, they've memorized "soap, rub, roll." But ask them to fix a drafting error next week, and you get blank stares. The scaffold of understanding never got built. What's worse, the instructor mistakes visible output for comprehension. "Look, everyone took something home!" That something, however, is a shallow echo of the technique. It crumbles under real pressure—new wool type, different humidity, a design tweak. I've seen this exact pattern in weaving workshops where warp tension issues emerge on day three, and nobody can untangle the root cause because they only learned the finish line, not the physics of the loom.

A product-first pace trades lasting mastery for a photo-op finish. That trade-off compounds. Every rushed workshop deposits a little less skill into each student's long-term reservoir.

Reputation Damage—Invisible Until It's Not

Here's what people rarely talk about: the brand rot. A workshop that consistently prioritizes the deadline over the craft becomes known, whispered about, as the place where 'you won't really learn.' That reputation spreads slowly through local art circles—but it clings. One instructor I worked with couldn't figure out why her weekend watercolor classes were losing traffic to a competitor who charged more and showed less. We polled past attendees: polite euphemisms like 'very structured' and 'made sure we finished.' Translation: no room to fail, no space to push the brush off the intended line. Her brand became synonymous with control, not creativity. And once that label sticks, it takes three seasons of patient, process-first rebuilding to shake it. Meanwhile, the competitor? They let students scrap three paintings before one clicked. Graduates left not with a framed canvas but with a repaired relationship with their own mistakes. That story travels.

One free, honest piece of advice from someone who has watched both models play out: if your workshop yields perfect products but hollow, anxious makers, you're not running a class. You're running a print shop. The real cost arrives the quarter nobody calls you back.

When You Actually Should Prioritize Product

Client-Driven Workshops With Strict Deliverables

Sometimes you don't get to choose the pace—the contract chose it for you. A corporate team-building workshop that must produce twelve usable canvases by 4:30 PM? That has a hard stop. A wedding-guest workshop where everyone needs a finished, framed piece to take home that night? Product becomes the non-negotiable floor. The trick is to distinguish between necessary product pressure and habitual product pressure. I once taught a two-hour logo-design crash course for a small business association—they needed vector files, not epiphanies. We tightened every exploratory exercise to ten minutes flat, demoed on a timer, and skipped sharing critiques in favor of direct instructor corrections. The catch is that you must name this trade-off aloud: "We're going for completion today, not depth. You'll get the technique, but you'll practice it later." Most participants actually relax when you admit the ceiling. They stop second-guessing their "bad" early decisions because you've collapsed the runway.

Portfolio-Building Short Courses

Here the product is the process made visible—a finished ceramic vase, a sewn garment, a printed zine that exists as a physical artifact. These courses run on a different clock entirely. Students enroll specifically to walk away with something they can photograph, submit, or sell. The pacing shifts from open-ended exploration to milestone-based production: Monday you throw the cylinder, Tuesday you trim and attach the handle, Wednesday you bisque-fire, Thursday you glaze. Miss a step and the kiln doesn't wait. That sounds harsh, but the clarity is its own kindness. One student told me after a five-day wheel-throwing intensive: "I hated the deadlines until I held the finished bowl. Then I realized I needed that pressure to stop second-guessing." What usually breaks first is the instructor's guilt. We want to let everyone find their flow, but portfolio courses demand a different generosity—the generosity of clear gates. Wrong order? Let them skip a warm-up to keep the kiln-load intact. But never pretend it's a process workshop when the brochure promised a product.

Quick reality check—do you actually have an emergency, or just an uncomfortable participant? I have seen instructors accelerate an entire session because one person was "falling behind," only to lose the other six who were finally reaching a flow state. That hurts everyone.

'The kiln closing at five o'clock was real. The anxious feeling that someone might not 'finish' on time was not.'

— potter with twenty years of community workshop experience

Emergency Time Crunches: Kiln Closing, Exhibition Deadlines, Venue Curfews

When the venue kicks you out at 9:00 PM sharp or the glaze kiln has a hard cutoff before a holiday, product pacing is survival pacing. These are the rare moments where you can ethically say: "Skip the deep reflection. Focus on the last three steps. Work fast, work clean, and we'll debrief by email." The pitfall is that emergencies become habits. I have watched workshop leaders treat every Saturday session like a fire drill—rush the underglaze, skip the cleanup demo, push students out the door with wet pots wrapped in plastic. That isn't an emergency; it's a poorly scheduled class. The distinction is objective: does the external constraint affect a physical outcome (kiln power-down, gallery submission deadline, rental overtime fee) or does it affect an emotional one (your own discomfort with silence)? If it's the latter, don't borrow the language of crisis. Say: "Let's pause. We have the time." The next time you face a real crunch, you'll have preserved your credibility—and your students will trust you when you say the clock actually is running.

FAQ: Common Questions About Workshop Pace

How do I handle a participant who works way slower?

You don't speed them up — you build a hinge into the schedule. I once taught a two-hour lino-cut workshop where one student barely carved a thumbnail, while three others had finished two prints. My first instinct was panic. But rushing that slow student would have trashed her confidence and produced a sloppy block she'd hate. Instead, I gave her a simple option: take the uncarved block home with a loaner tool, or switch to a pre-drawn design I'd prepped as backup. She chose the block, finished it at her kitchen table, and emailed me a photo of a gorgeous print. The catch is preparation — you need that backup plan ready before the workshop starts. Loose sheets of tracing paper, a second simpler motif, or even a half-carved block you can hand over. That's not coddling; it's respecting that their pace isn't wrong — it's just different from your clock.

What if students demand more finished pieces?

Then you're negotiating a legitimate tension. They paid a fee — they want something frameable. The trick is redefining what counts as "finished." Not a lie, just a shift: a single well-honed piece beats three sloppy ones every time, and you can prove it. Quick reality check — pull out one of your own early multi-project rush-jobs and a later single focused piece. Show them side by side. I've watched rooms go quiet when people see the difference clearly. But don't fight them outright. Offer a middle path: structure the workshop so the first 70% of time builds core skills carefully, and the final 30% becomes an open studio sprint where they apply everything to a fast second piece. They get two outcomes — one deep, one quick — and you keep the process intact where it matters most.

Can I switch pace mid-workshop?

Yes, but only if you announce it as an intentional pivot, not just frantic course-correction. Nothing kills trust faster than an instructor who seems lost. A clean switch sounds like: "Okay, we've spent forty minutes really settling into the shading technique. Now I'm shifting us into a timed draft — ten minutes, no erasing, just commit to one shape. Go." That's a gear change, not a panic brake. What usually breaks first is your own comfort — instructors default to rush mode when they sense the group is drifting. Resist that. Instead, insert a five-minute pause where everyone steps back, looks at their piece from three feet away, and breathes. That tiny reset often recalibrates the room's tempo without you touching the schedule. One final note — don't switch pace more than twice in a three-hour session. More than that and you're just confusing people, not protecting any process at all.

“I protect the slowest student in the room. That pace becomes the container everyone else trusts.”

— workshop leader, letterpress studio, after a 4-hour typesetting session

What do I say when someone finishes way too early?

Don't hand them more materials. That teaches them speed is the reward. Wrong order. Instead, hand them a magnifying glass and ask them to find one flaw in their own work — not to fix it, just to see it. The point isn't busywork; it's building an eye for nuance. Early finishers are often the ones who need slowing down most, and your job is to show them that stopping doesn't mean done. If they truly can't find anything, fine — let them observe others quietly. But I've never seen a beginner's piece that couldn't benefit from another five minutes of honest looking.

Summary: Your Next Three Experiments

Try one 'process-only' session with no final product

Scary, right? A two-hour workshop where nobody walks out with a finished thing. The catch is that you must tell participants upfront: We're not making anything today. We're wrecking things, testing limits, and chasing dead ends. I ran a watercolor workshop last spring where every student had to paint badly on purpose—lay down muddy washes, scrape them off, then paint over the wet mess. One woman nearly walked out at minute five. By minute forty she was laughing at how little control she had. That session taught me more about color and risk than any polished piece ever could. The absence of a product is the whole point; it lets the brain explore without the internal editor screaming Fix it, finish it, frame it.

Add a 10-minute 'stuck time' buffer to your next workshop

Your lesson plan says 45 minutes for the main exercise. Trim it to 35. Then label those last ten minutes as deliberate dead air. Not a break—stuck time. Students hit a wall, set their tools down, and simply stare at what they've made. No instructor rescue, no prompt, no "try this technique." What usually breaks first is the silence. Someone picks up a brush again, but slower. Someone else flips their paper sideways. The production line pressure evaporates because the clock says stuck is part of the schedule. That buffer cost me nothing except the discomfort of watching people struggle—but I stopped seeing struggle as failure after the third workshop where the best work emerged during that idle slot.

Ask students one question: 'What did you learn that you didn't expect?'

Skip the standard critique. No rubrics, no "what works well / what needs improvement." Instead, at the end, pose that single question. The answers will gut you: I learned that my hand moves faster than my anxiety or I didn't expect the mistake to be the interesting part. This question flips the focus from product evaluation to process revelation. The tricky bit is you must not judge the answers—just collect them. I tape index cards to the wall now. One student stared at her card for three minutes and wrote nothing. Then she crossed out the question and wrote: I learned I'm afraid of messing up a blank page. That sentence taught me more about workshop design than any pacing diagram ever could.

The product is what you carry home. The process is what you carry forward. Most workshops optimize for the wrong bag.

— overheard at a ceramics studio, after a kiln failure ruined everyone's final pieces