Skip to main content

By Alex Bolotovsky, CEO of J Leaders

 

Parsha in a Nutshell

Parashat Naso opens with the ultimate logistical breakdown: how to dismantle and transport the heavy Tabernacle through the desert. Moses splits the workforce into teams with strict lanes. One team carries the sacred vessels, another handles the tapestries, another the structural beams, pillars, and bases. The Torah explicitly commands that they must assign the inventory by name down to every single peg and socket (Numbers 4:32).

Diving Deeper

In the startup and corporate worlds, we talk a lot about “cross-functional collaboration.” But blurry boundaries create the Tragedy of the Commons. When a project slips through the cracks, everyone points fingers because “the team” was supposed to handle it. The Torah cuts through this chaos with the obsessive detail.
By assigning every single piece of infrastructure to a specific person by name, Moses ensured absolute accountability. If a tent peg was missing at the next campsite, everyone knew exactly who dropped it.

This ties directly into the second half of the Parsha, where the twelve tribal leaders bring identical dedication gifts over twelve days. The text repeats the exact same list word-for-word twelve times which is a total slog to read. Building a team means valuing the routine and equally valuing and acknowledging everyone’s contributions. Carrying a peg isn’t glamorous, and running the same playbook every day isn’t flashy but if these tasks aren’t done, the whole tent.

Weekly Leadership Challenge

  1. Assign the Pegs: Look at a project your team is launching this week. Is there a blurry task that “the team” is collectively working on? Stop the ambiguity. Assign that specific “peg” to someone by name.
  2. Let Go of the Heavy Lifting: If you are a manager, look at your to-do list. This week, hand off one recurring logistical task. Give them the context, give them the ownership, and step back.
  3. Validate the Infrastructure: Take five minutes to thank the person on your team who handles the “unsexy” work: the QA testing, the data entry, or the scheduling.